TEST: use K64F replace DISCO_L475VG_IOT01A to run some example test

[jamesbeyond]

Summary of changes

DISCO_L475VG_IOT01A being slightly overloaded on building/running examples. because it been used heavily on BLE tests.
Also due to DISCO_L475VG_IOT01A not having default connectivity devices.
and NUCLEO_F429ZI not having default storage devices, some CI tests are failing, so
in someplace try to replace those 2 targets with K64F for building and running the examples

Impact of changes

Migration actions required

Documentation

No documents changes required

---

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

---

[ciarmcom]

@jamesbeyond, thank you for your changes.
@ARMmbed/mbed-os-tools @ARMmbed/mbed-os-maintainers please review.

[0xc0170]

DISCO_L475VG_IOT01A being slightly overloaded on building/running examples.

This just fixing the load of CI - not actual failures?

[0xc0170]

Making sure this should be in 6.0.0 alpha1 or not.

[jamesbeyond]

Making sure this should be in 6.0.0 alpha1 or not.

Please mark it as 6.0.0 alpha1 , thanks

[adbridge]

Making sure this should be in 6.0.0 alpha1 or not.

Please mark it as 6.0.0 alpha1 , thanks

Talking to @jamesbeyond this is a CI only fix so marking for alpha 2

[0xc0170]

Please add to the commit msg why are we changing these targets, the intention is missing.

As I understood from the answers here, the load on some targets its high and this should balance it better?

[jamesbeyond]

comment messages have been updated. @0xc0170

[0xc0170]

CI started

[mbed-ci]

Test run: SUCCESS

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