ci: Use new mbed-os-env docker image in "multiple executables" test ...

The github workflow to test building multiple executables was using the
soon to be deprecated docker image "mbedos/mbed-os-env:latest". This
commit points it at the new docker image on ghcr.io.

targets: Add "bare-metal" to supported_application_profiles ...

We weren't setting the "supported_application_profiles" correctly for
some baremetal supported targets. This didn't cause build failures with
mbed-cli 1 as it just seems to ignore this config parameter. In our CMake
build system we have added a hard dependency on the
supported_application_profiles; we fail the build if the profile we're
trying to build isn't in the list.

CMake: Use CMAKE_MODULE_PATH to locate nuvoton post build hook ...

We were previously relying on the global MBED_PATH variable to provide
the root for the include path to the post build hooks. We can't
guarantee that MBED_PATH will be set by any application building us, so
use CMAKE_MODULE_PATH (which we always set) like we do for the other
post-build hooks.

ci: Add github action to build greentea tests with cmake ...

Build for two targets, one with baremetal profile and one full profile.

CMake: greentea: Use more specific name for baremetal option ...

Make it obvious the option is used for greentea tests.

CMake: greentea: Port mbed-drivers-ticker to CTest ...

Call add_test in mbed_greentea_add_test and specify mbedhtrun as the
command to run.

An MBED_HTRUN_ARGUMENTS variable has been added, which is a semicolon
separated list of arguments to forward to htrun. The user is required to
pass in any arguments mbedhtrun needs to communicate with the device
under test at CMake configuration time.

We automate passing some of the htrun arguments in CMake using data
provided by mbed_config.cmake or gathered from the CMake environment.
The following arguments are passed to htrun from CMake:

* -f/--image-path
* -e/--enum-host-tests
* -m/--micro
* -R/--reset-timeout

--baud-rate is also passed if the MBED_CONF_PLATFORM_STDIO_BAUD_RATE
config parameter is defined.

Temporary checks have been added to mbed_greentea_add_test to keep the
old flow working until we port all of the greentea tests to CTest. These
checks should be removed after we make all greentea tests runnable by
CTest.

CMake: greentea: Set variables usually defined by external apps ...

We rely on external applications to set MBED_CONFIG_PATH and include
app.cmake. Mbed OS can't build for a target without those parameters
set. When building greentea tests there is no external application. So,
we define the appropriate settings in our root CMakeLists.txt for
greentea tests.

CMake: Add option to enable greentea tests ...

Add an option to enable the greentea tests independently from the unit
tests.

We can't just use the typical BUILD_TESTING option to enable greentea
tests. BUILD_TESTING enables unit tests and fetches googletest, which
are compiled for the host. Greentea tests are cross compiled and require
a toolchain file. For this reason we add a new option just to enable
greentea tests, preventing build failures triggered by the unit tests
and googletest.

Merge pull request #14983 from LDong-Arm/sfdp_sector_map ...

SFDP: Add unit tests for Sector Map Parameter Table parsing

SFDP: Add unit tests for Sector Map Parameter Table parsing ...

Add tests for `sfdp_parse_sector_map_table()` which currently (at the
time of this commit) supports flash devices with
* no Sector Map Parameter Table (i.e. the whole flash is uniform and
non-configurable)
* a single descriptor in the Sector Map Parameter Table (i.e. the
flash layout is non-configurable and has multiple regions)

Support and unit tests for flashes with multiple configurable layouts
will be added in the future.

Note: The implementation of `sfdp_parse_sector_map_table()` assumes
the table to be valid if read succeeds, so the SFDP reader callback
needs to ensure it reads data correctly or return an error.

SFDP: TestEraseTypeAlgorithm: Move setup into test case ...

The test data `struct mbed::sfdp_smptbl_info smptbl` is only relevant
to `TestEraseTypeAlgorithm` and not shared with other test cases.

SFDP: Set region count to 1 for no sector map ...

A flash device with no sector map table has uniform sectors, and we
treat the whole flash as one region. In this case the function
`sfdp_parse_sector_map_table()` sets the single region's size and high
boundary accordingly, but it lacks setting of region count to 1, so
users of the SFDP parser may not get the correct number of regions.
This commit fixes the issue.

Merge pull request #14980 from saheerb/master ...

github action fix for uppercase repository owner

Merge pull request #14979 from moshe-shahar/patch-1 ...

requirements.txt - remove manifest-tool 1.5.2 and mbed-cloud-sdk

github action fix for uppercase repository owner

requirements.txt - remove mbed-cloud-sdk

Update LICENSE.md

Merge pull request #14978 from jamesbeyond/fix_docker ...

DOCKER: fix a bug in docker building GHA

requirements.txt - remove manifest-tool 1.5.2

SFDP: Move handling of no sector map into `if` ...

When a flash chip's SFDP table has no sector map, we treat the whole
flash as a single region. As an optimization, this should only be
done if there is indeed no sector map.

DOCKER: fix a bug in docker building GHA

Merge pull request #14952 from saheerb/master ...

github actions for mbed-os-env docker management

Merge pull request #14929 from LDong-Arm/move_target_h ...

Unit tests: Move target_h/ stubs into libraries' test doubles

github actions for mbed-os-env docker management

Travis: Enable maximum verbosity of pinvalidate.py ...

Run pinvalidate.py with -vvv to print the cause of failure, making
it easier for authors of pull requests to fix pin names.

Unit tests: Fix pin validation failure ...

The test script pinvalidate.py requires the following which are
missing in the unit test stub PinName.h:
* A comment "MBED TARGET LIST"
* `CONSOLE_TX` and `CONSOLE_RX` in the `PinName` enum

This commit adds them.

Unit tests: Remove redundant CMake target mbed-headers-base ...

Individual libraries' `target_h` stub headers have now all been moved
from `mbed-headers-base` to `mbed-headers-<library>`.

Note: Even though headers previously in `target_h` are technically
stubs/fakes too, they are used by not only unit tests but also regular
libraries when compiled for unit tests, because no target-specific HAL
implementation exists in this case. In order for regular library
sources to pick up `target_h` headers, those headers must

* have the same names as regular headers
* appear first in include paths

This is why those headers are part of `mbed-headers-<library>` and not
`mbed-stubs-<library>`. Before this refactoring, `mbed-headers-base`
was the first in unit tests' include paths.

Unit tests: Fix style in hal gpio_object.h stub

Unit tests: Move hal target_h stubs ...

Stubs previously in UNITTESTS/target_h/ have the same names as
regular Mbed OS headers, intending to override the latter directly.
We move hal target_h stubs into hal/tests/UNITTESTS/doubles/.

Note: In Mbed OS, the standard include format requires each header to
be prefixed with its module name, for example "hal/gpio_api.h". This
requires headers to be organized in a module directory. But unit tests
stubs for hal correspond to what a real Mbed target would have
implemented (in a non-test scenario), and targets do not currently put
headers in hal/, so we similary put stub headers directly in
hal/tests/UNITTESTS/doubles/ instead of add a hal/ subdirectory there.

Unit tests: Move randLIB.h ...

The stub header randLIB.h overrides the header of the same name in
platform/randlib/ which is an external repository vendored into
the mbed-os codebase. As the repository is synchronized regularly,
it is better not to put overrides there, so we put the randLIB.h
stub into the regular platform doubles directory.