github actions for mbed-os-env docker management

Merge pull request #14948 from Patater/lorawan-timer-unittest-fake-fix ...

Fix lorawantimer unit test

test: Make MBED_ASSERT failures fail ...

Make MBED_ASSERT failures fail the unit test case. Without this, we
might not notice the assertion failure as it wouldn't be bubbled up to
googletest.

test: CircularBuffer: Don't push zero elements ...

The CircularBuffer doesn't allow pushing zero elements; you must push at
least one. Update the CircularBuffer unit test to avoid invalid use of
the CircularBuffer.

test: lorawanstack: Use valid message type ...

We previously made up an invalid message type, which was roughly
`MCPS_MULTICAST | 0x40`. This causes an MBED_ASSERT failure in the
handle_rx function, as it uses an assert to validate the message type
passed to it (in convert_to_msg_flag()). Use the valid message type
MCPS_MULTICAST instead in the handle_rx unit test.

unittests: Test_LoRaWANTimer.start: Fix test failure ...

We weren't initialising the mocks correctly, so an MBED_ASSERT failed in
`LoRaWANTimer::start` because the "timer_id" was not set.

Merge pull request #14397 from macronix/macronix_spi_NAND ...

add SPI NAND Block device driver

Merge pull request #14831 from jeromecoutant/PR_DISCO_WB_LED ...

DISCO_WB5MMG: add RGB LED

Merge pull request #14945 from OpenNuvoton/nuvoton_tfm_missing_update ...

TFM: Add missing IPC file for PSA Firmware Update

Merge pull request #14953 from LDong-Arm/post_build_hook_rework ...

Rework post-build to support multiple executables

DISCO_WB5MMG: add RGB LED

Merge pull request #14914 from nicole-osaz/my_mbed-os_branch ...

Deprecate the Greentea metrics API

TFM: Add missing IPC file for PSA Firmware Update ...

On a target that doesn't support Firmware Update, compilation still works, and any attempt to call the Firmware Update API returns a runtime error which is good enough.

equeue: Enable use of stub from C++ ...

Add extern "C" to the equeue_stub declaration to avoid an error when a C
file implements the equeue_stub symbol (as we do in equeue_stub.c).

    Undefined symbols for architecture x86_64:
      "_equeue_stub", referenced from:
          Test_LoRaWANTimer_start_Test::TestBody() in Test_LoRaWANTimer.cpp.o
    ld: symbol(s) not found for architecture x86_64
    clang: error: linker command failed with exit code 1 (use -v to see invocation)

CMake: Add test for multiple-executable support ...

Add a test to build two executables in two directories under a single
project.

Cypress: Improve `mbed_post_build_psoc6_merge_hex()` ...

The CMake macro `mbed_post_build_psoc6_merge_hex()` takes the name of
a Cypress target and an optional Cortex-M0 hex image as arguments. The
proper way to define and parse optional arguments of a function or
macro is `cmake_parse_arguments()`, which allows the caller to
indicate what they are passing rather than rely on an argument's
relative position within `${ARGN}` which is not rigorous.

Also, avoid duplicating the common part of the post build command
when the optional argument is passed/not passed.

Rework post-build to support multiple executables ...

When building greentea tests, each test is an executable with its
own output binary path. This is also the case when a user project
produces multiple executables. But the current implementation of
post-build operations always assumes there's only one executable,
at the root of the build directory.

The post-build command depends on Mbed target, and it always takes
the the executable we build as an input file. To achieve this, we
let each Mbed target (that has a post-build command) define a function

    function(mbed_post_build_function target)

which takes a CMake executable target as an argument from which it can
get its binary path using generator expressions. It generates and adds
to the passed executable target a post-build custom command.

Notes:
* The function name needs to be exact, because CMake only supports
literal function calls - CMake can't dereference a function name from
a variable. To avoid multiple definitions of this function, each Mbed
target needs to guard it with a macro to check if the user is
building this Mbed target.
* `mbed_post_build_function()` is a function, but it is usually
defined by another macro rather than a parent function, because
nesting functions would make many variables inaccessible inside the
innermost `mbed_post_build_function()`.
* There's no more need to force regenerate images. Previously, post-
build commands were custom *targets* which always got to run, so we
force regenerated images on every build to avoid patching an image
that's already been patched once on previous build. Now post-build
commands are custom *commands* of the same executable target, and they
are only run if the executable target itself is rebuilt.

cmake: Avoid linking to gcov ...

Use the `--coverage` option instead of manually linking to gcov, as some
host platforms (like macOS, FreeBSD) don't have gcov by default and use
an llvm equivalent instead.

equeue: Add missing header guards ...

The header equeue_stub.h was missing header guards to enforce single
inclusion. Add some header guards.

cmake: Remove trailing whitespace ...

Remove trailing whitespace from lorawantimer's CMakeLists.txt.

Merge pull request #14939 from jeromecoutant/PR_PIN_ALIAS ...

Standard Pin Names validation script update

pinvalidate.py script: add deprecated ARDUINO test

pinvalidate.py script: add SPI and I2C alias check ...

Goal is to follow
hal/include/hal/PinNameAliases.h

pinvalidate.py script: remove spaces

CMake: Move post build functions out of root CMakeLists.txt ...

The 'post build' functions are made visible by adding the mbed-os
subdirectory. This is not ideal as any components in mbed-os wishing to
call the functions must be added after the functions are defined. To
improve modularity move these functions to a separate CMake script.

We include the post build CMake script in app.cmake for now so we don't
break user's projects.

Merge pull request #14940 from Patater/update-prettytable ...

python: Allow newer prettytable with newer python

python: Allow newer prettytable with newer python ...

This helps to allow installation of Mbed OS's Python requirements, when
CMake is used, into the same Python environment as mbed-os-tools. The
versions specified here are aligned with mbed-os-tools;
tools/cmake/requirements.txt depends on the same version of prettytable
as mbed-os-tools's requirements.txt.

python: Remove direct dependency on prettytable ...

Mbed CLI 1 parses the base requirements.txt and attempts to
automatically install missing python libraries for you. Unfortunately,
it's requirements parser is not as capable as the one shipping with pip.
In particular, we are unable to express different version of libraries
conditional on the version of Python being used.

    ---
    [mbed] ERROR: Unknown Error: Unsupported environment marker:  python_version < '3.6'

Remove the direct dependency on prettytable from requirements.txt, as
mbed-os-tools depends on prettytable and we can pick up the dependency
(as properly expressed conditionally on the Python version) from there,
without having to use the limited requirements parser in Mbed CLI 1.

Merge pull request #14730 from Ekidna/fix/sx126x-select-pins ...

Add config macros for device-variant, freq-support and xtal config

Merge pull request #14912 from ARMmbed/move_unittest_ble_headers_lib ...

Move ble stubs to FEATURE_BLE lib