Update mbed-coap to version 4.3.0

[anttiylitokola]

Description

Add new API to clear whole sent blockwise message list.

Pull request type

• Fix
• Refactor
• New Target
• Feature

[anttiylitokola]

@yogpan01 something to review.

[cmonr]

Wawiting on review from @yogpan01, but will start build now.

/morph build

[cmonr]

@0xc0170 Dunno why, but gonna need you to start morph...

@studavekar fyi.

[yogpan01]

@0xc0170 Can this be taken into one of the mbedOS 5.8 Release candidates ?

[studavekar]

/morph build

[studavekar]

@cmonr did something changed with ur gitbub account by any chance ?

[cmonr]

@studavekar Not that I'm aware of. Still part of the same groups.

@yogpan01 @adbridge Would be the one to make that final call, but as a rule of thumb, the only PRs that should make it into an Release Candidate after RC1 has been made are bug fixes to the Release Candidate.

[adbridge]

@yogpan01 I'm afraid this has missed the boat for mbed-os 5.8 and this looks like it is adding a new API which means it will need to wait until 5.9. @cmonr was correct in his assertion above. Feel free to plead your case to @sg- or @ChiefBureaucraticOfficer once the first release candidate is cut we should not be taking any new code.

[mbed-ci]

Build : SUCCESS

Build number : 1362
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/6171/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build
/morph mbed2-build

[mbed-ci]

Test : SUCCESS

Build number : 1142
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/6171/1142

[mbed-ci]

Exporter Build : SUCCESS

Build number : 1014
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/6171/

[yogpan01]

@adbridge @0xc0170 Please refer to my comment on here #6357 (comment)
This comment is valid also for any mbed-coap commits. These are internal changes and have no impact on any mbedOS API beahviour since they are used by Client for its own purpose. We ensure that these are backward compatible with each release (it has been backward compatible for last 2 years) and we provide promise for not changing API in breaking way otherwise it will go to Major release of mbedOS , we follow semantic versioning there. To get minor release of this library into mbedOS shouldn't have to wait for major release , the cycle is too long for client.
Hence, please take this one also for 5.8.1 candidate.

[adbridge]

@yogpan01 We will take 4.3 and 4.4 into 5.8.1, however please be aware of the following:
Adding a new feature / API that is available to users go to minor releases irrespective of backward compatibility. We will soon update our guidelines on what each of the checkbox options mean and exactly what can and cannot be taken to a patch release. That, along with your help to ensure things are marked correctly will help to ensure a smoother flow going forward.

[mbed-ci]

Exporter Build : FAILURE

Build number : 1219
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/6171/