tools: fix SPDX identifiers

Merge pull request #11904 from jamesbeyond/HW_gcov ...

TOOLS: enable build greentea test coverage for HW

Enabling small C library option and deprecating uARM toolchain ...

- By default, Mbed OS build tools use standard C library for all supported toolchains.
   It is possible to use smaller C libraries by overriding the "target.default_lib" option
   with "small". This option is only currently supported for the GCC_ARM toolchain.
   This override config option is now extended in the build tool for ARM toolchain.
 - Add configuration option to specify libraries supported for each toolchain per targets.
 - Move __aeabi_assert function from rtos to retarget code so it’s available for bare metal.
 - Use 2 memory region model for ARM toolchain scatter file for the following targets:
   NUCLEO_F207ZG, STM32F411xE, STM32F429xI, NUCLEO_L073RZ, STM32F303xE
 - Add a warning message in the build tools to deprecate uARM toolchain.
 - NewLib-Nano C library is not supporting floating-point and printf with %hhd,%hhu,%hhX,%lld,%llu,%llX
   format specifier so skipping those green tea test cases.

minimal-printf: Enable using a target configuration parameter

TOOLS: fix failed python test

Permit non-TrustZone ARMv8 build ...

Change the heuristic for selection of CMSE in the tools python, so that
a non-TrustZone ARMv8 build can happen.

Ideally we would have more direct flagging in the targets, but this
refines the heuristic so the necessary behaviour can be easily
achieved.

* DOMAIN_NS=1 is based purely on the `-NS` suffix on the core name.

* Enabling CMSE in the compiler and outputting a secure import library
  is now enabled when the core doesn't have an `-NS` suffix by either
  the target label `TFM` being present or the flag `trustzone` being set.

This covers the existing ARMv8-M behaviour - TF-M builds have the TFM
label, as per its documentation; M2351 secure builds have no explicit
flagging, so we ensure that the M2351_NS target has the trustzone flag
set, and the out-of-tree secure target inherits that.

Tools: Add "Cortex-M33E" option ...

There was a gap in our pattern - we didn't offer M33 with DSP Extension
but no floating-point.

Correct some CPU selections in tools ...

* For ARMC6, core types `Cortex-M4` and `Cortex-M7` did not explicitly
  add `--fpu=none`, so it defaulted to assuming FPU present. This would
  cause a compilation error if the target's cmsis.h had `__FPU_PRESENT`
  defined to 0.

* For GCC, `Cortex-M33FE` did not include `+dsp` in the architecture
  selection.

* For ARMC5 and ARMC6, `Cortex-M0+` did not pass `M0plus` to the
  non-Clang tools.

Fix pylint in iar.py except for the long regex

Move toolchain base class into another file

Remove use of hooks from IAR ...

Aparantely I missed this previously

Simplify hook tool implementation ...

The "hook tools" were capable of hooking into many commands run by the build system.
To my knowlage, the only hook is the "post-build-hook". The post build hook could be
easier to reason about if the implementation is specialized for just post-build
hooking.

This commit make it much easier to point out where post build hooks are called by
making the call explicit.

Set IAR version as 8.32 in tools

Add missing space - coding style nit ...

Co-Authored-By: deepikabhavnani <deepika.bhavnani@arm.com>

Set the DSP option as `E` for Cortex-M33

Correct the floating+dsp options for Cortex-M processors ...

As per the IAR Development guide, below options for CPU are valid

1. Cortex-M33
2. Cortex-M33.no_dsp (core without integer DSP extension)
3. Cortex-M33.fp (floating-point unit with support for single precision)
4. Cortex-M33.no_se (core without support for TrustZone)
5. Cortex-M4
6. Cortex-M4F
7. Cortex-M7
8. Cortex-M7.fp.dp (floating-point unit with support for double precision)
9. Cortex-M7.fp.sp (floating-point unit with support for single precision)

Update `cmse` flag based on core_arch instead of different cores

Update IAR flags for Armv8M devices. ...

Cortex-M23 / Cortex-M33 CPU settings for baseline and mainline
profile (with optional floating and dsp options) updated.

Added encoding to version check for Py3 compat

TOOLS : Add missing M33 and M33F in python scripts

Track supported information within toolchain clasess

Merge pull request #7876 from cmonr/version-warn-not-err ...

Tools: Modified version mismatch msg to be warning instead of error

Remove IAR assembler macros containing quotes ...

IAR assembler 7.80 has some problems handling difficult macros, leading
to immediate exit with return value -11.

In particular, a URL string has been causing problems, presumably due to
the "//" resembling a comment.

A previous escaping workaround in 0d97803 seemed to work, but the crash
has still been seen with a particular target.

Previous creation of the extended command line file for the IAR
assembler was stripping quotes from macros. This rendered the resulting
definitions for string-containing macros incorrect, which means that we
can assume no assembler code is currently relying on them.

Therefore, as a precautionary measure to avoid the crash, simply remove
all macros containing strings when creating them for IAR. This
apparently clears the crashes seen during testing of
https://github.com/ARMmbed/mbed-os/pull/8023

Merge pull request #8017 from TTornblom/master ...

IAR: Fix for #7662, only massage the error decode URL for the IAR .xcl

IAR: Fix for #7662, only massage the error decode URL for the IAR .xcl ...

file.

Fix memory reservation for Softdevice in NRF52_DK

Modified version mismatch msg to be warning instead of error

Merge pull request #7061 from TTornblom/master ...

Tools: Include configuration in ASM

Correct string usage in version checking

Use via file for ASM macros in IAR