Remove the deprecated CAN APIs.

[rajkan01]

Summary of changes

Removed CAN deprecated APIs.

Impact of changes

With these changes, CAN attach APIs with cv-qualifiers sources are removed and this is the breaking changes for the user

Migration actions required

Use attach(callback(obj, method), type)

Documentation

---

Pull request type

[] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[x] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers

@evedon

---

Pull request has been modified.

[0xc0170]

Can each of this functionality be in a separate commit ?

[rajkan01]

Can each of this functionality be in a separate commit ?

We have decided to keep in one PR until if those deprecated APIs has a dependency.

[ciarmcom]

@rajkan01, thank you for your changes.
@evedon @ARMmbed/mbed-os-maintainers @ARMmbed/mbed-os-core please review.

[0xc0170]

I don't see the dependencies here between them, however my point was to split commits at least, not PR itself.

[0xc0170]

I don't see the dependencies here between them, however my point was to split commits at least, not PR itself.

@rajkan01 What do you think about this one - I failed to see the dependencies so could be in this PR just separate commits.

Let's progress with this removal

[bulislaw]

Also it's a major breaking change.

[bulislaw]

Please split it into one PR per area, all of them should be major breaking and have the summary/impact/migration sections filled in.

[0xc0170]

@rajkan01 Already not in the docs? (no docs PR needed) ?

[0xc0170]

CI started

[mbed-ci]

Test run: FAILED

Summary: 1 of 11 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

• jenkins-ci/mbed-os-ci_cloud-client-pytest

[evedon]

@rajkan01 Please confirm that a doc PR is not needed (i.e. documentation changes will be automatically made by doxygen engine) ?

[0xc0170]

client test restarted

[rajkan01]

@rajkan01 Please confirm that a doc PR is not needed (i.e. documentation changes will be automatically made by doxygen engine) ?
@evedon It seems to be no documentation changes required in Mbed-os-5-docs, and Doxygen source code documentation has taken care by Doxygen engine docs generator.

[mergify]

This PR does not contain release version label after merging.