CMake: Fix the listing of system_clock.c for STM32F413xH

[hugueskamba]

Summary of changes

Each variant now has its own system_clock.c file.
Therefore ensure the correct one is added for each variant.
Also reduce the number of CMakeLists.txt file as each
variant does not have significant number of files.

Impact of changes

Migration actions required

Documentation

---

Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] 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

---

[0xc0170]

I am addressing Travis failures with py3.5 in a separate PR. I've noticed it started failing just recently.

Pull request has been modified.

[0xc0170]

travis fix is on master. Please rebase all your PRs, it should fix it

[hugueskamba]

travis fix is on master. Please rebase all your PRs, it should fix it

Done.

[0xc0170]

It's unfortunate but the move triggered astyle error, it is trivial to fix. Can you please?

[hugueskamba]

It's unfortunate but the move triggered astyle error, it is trivial to fix. Can you please?

Done.

[0xc0170]

astyle still reports one (blank space on the line?)

[hugueskamba]

astyle still reports one (blank space on the line?)

Done.

[0xc0170]

Travis can't compile events:

./connectivity/drivers/cellular/TELIT/HE910/ONBOARD_TELIT_HE910.cpp:127:9: error: 'MDMRTS' was not declared in this scope
  127 |     if (MDMRTS != NC && MDMCTS != NC) {
      |         ^~~~~~
./connectivity/drivers/cellular/TELIT/HE910/ONBOARD_TELIT_HE910.cpp:127:25: error: 'MDMCTS' was not declared in this scope
  127 |     if (MDMRTS != NC && MDMCTS != NC) {

please review

[hugueskamba]

This force-push moves ONBOARD_TELIT_HE910.cpp back to the
TARGET_MTS_DRAGONFLY_F413RH directory as it causes a build failure since
the file has STM specific symbols which cause non STM Mbed targets to fail
when building with the TELIT cellular driver.

[0xc0170]

CI started

[mbed-ci]

Jenkins CI Test : ✔️ SUCCESS

Build Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

CLICK for Detailed Summary

jobs	Status
jenkins-ci/mbed-os-ci_unittests	✔️
jenkins-ci/mbed-os-ci_cmake-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-test	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️