rtos: fix delay with 0 ...

Fixes error osErrorParameter that triggers our assert.
RTX delay ignored 0 previously, it now returns osErrorParameter instead.

cmsis: patch fpu in asm for armcc5 ...

For FPU, use armasm to select fpu selection. This will be fixed upstream in the next version of CMSIS. Meanwhile, we use our local patch.

Taken from --cpu selection for armasm:

--cpu           | {FPU}
Cortex-M4.fp.sp | VFPv4_SP_D16
Cortex-M7.fp.sp | FPv5-SP
Cortex-M7.fp.dp | FPv5_D16

Tracking issue: https://github.com/ARM-software/CMSIS_5/issues/1266

cypress: fix cy_syslib breakpoint undefined ...

CMSIS 5.8.0 requires for armcc to include compat header prior any other header.
See Known issues for the release.

cmsis: preprocess irq files ...

We use preprocessor for asm files even for Armcc. If symbol is defined it's replaced by preprocessor,
asembler would just see 1 or 0 in this case and errors:
TARGET_M33\\irq_armv8mml.S", line 31: Error: A1185E: Symbol missing

Use preprocessor instead.

musca targets: use IsException instead of removed isIrqMode

cmsis: fix armcc compat header redefition of enable/disable irq ...

The fix will be in the 5.8.1 CMSIS, we cherry-pick it to our imported version.
See https://github.com/ARM-software/CMSIS_5/commit/e797cca3f42bef19a2c33b3b929f6010ddf53580

cmsis: fix rtx_def inclusion in .S files for Gcc Arm ...

rtx_def includes two CMSIS headers that pull in C/C++ headers in our case. As I found out,
they should only define macros. We can fix it but it will require some refactoring as our targets
use mbed rtx headers to define heap using stdin header, plus some other offenders.

Workaround is to exclude the headers we do not need in irq assembly files.

Tracking issue https://github.com/ARMmbed/mbed-os/issues/14962

semihosting: add compat header where is required ...

ARMCC provides __semihost via compat header. As CMSIS 5.8.0 removed this compat header,
we need to explicitly include it to fix definition missing error.

retarget: move compat header for ARMClang prior any cmsis headers ...

Reference: CMSIS 5.8.0 known issues and https://github.com/ARM-software/CMSIS_5/issues/1211

This fixes the error about redefinition of enable/disable irq. we need compat header because of
semihosting (not yet provided in CMSIS).

cmsis: fix license header in rtx_def ...

Upstream fix was merged https://github.com/ARM-software/CMSIS_5/pull/1238. Included here as it will be overwritten once again updated

cmsis: importer sha removal ...

I had to resolve conflicts with these sha. CMSIS 5.8.0 includes fixes and makes these changes
irrelevant.

CMSIS/RTX: Allow overwriting mutex ops for ARMC ...

(cherry picked from commit 08ab8cc)

CMSIS/RTX: Patch to conditionally compile ...

tz_context.c should be compiled only for secure world,
definition of API's in tz_context.h should be part of secure
binary/bootloader when building mbed-os as non-secure

(Cherry picked from d0a43b8)

(cherry picked from commit fb35475)

CMSIS/RTX: Patch RTX4 to preserve osThreadDef compatibility ...

mbed OS used older RTX4 version and with osThreadDef accepting only 3
parameters, to preserve compatibility we hardcode the 'instances'
parameter to 1.

(cherry picked from commit 428acae)
(cherry picked from commit 4360b7b)

[CMSIS_5]: Updated to 13b9f72f2

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.

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.

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.