minimal-printf: Add capability to run floating point tests manually

[hugueskamba]

Description

There is currently no way for the CI to test features that are disabled by default. This PR provides a way to run the existing floating point tests manually by providing a configuration file that overwrite the default value of the attribute that disables floating point support in minimal-printf.

Floating point support is set to false by default here.

Pull request type

[ ] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[X] Test update
[ ] Breaking change

Reviewers

@jamesbeyond @evedon

Release Notes

[ciarmcom]

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

[0xc0170]

I assume this is preferred way to run various CI jobs (having configuration in the codebase rather than in CI).

[evedon]

This is the first step towards testing features that are disabled by default.
Next, we need to bring this in CI.

[0xc0170]

cc @OPpuolitaival

[0xc0170]

CI started

[mbed-ci]

Test run: FAILED

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

Failed test jobs:

• jenkins-ci/mbed-os-ci_build-GCC_ARM

[0xc0170]

Ci restarted, internal fault

[mbed-ci]

Test run: SUCCESS

Summary: 4 of 4 test jobs passed
Build number : 2
Build artifacts

[0xc0170]

@ARMmbed/mbed-os-test @jamesbeyond Please review

this will need CI enablement as the next step as mentioned earlier.

[jamesbeyond]

This looks good to me. I guess @OPpuolitaival will need to figure out the possible way to enable it in the CI