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: 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.

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: Move drivers target_h stubs

Merge pull request #14941 from hazzlim/update-tests-to-use-chrono ...

Update references to time values to use chrono

Greentea: Remove deprecated APIs and use chrono ...

References to time should do so using std::chrono. We reworked tests in
connectivity and drivers to use std::chrono and new APIs in order to
remove deprecation warnings resulting from deprecated API calls.
This required addition of  a macro for test assertions using std::chrono
values.

As host test "timing_drift_auto" expects time values represented as an
integral number of microseconds, we explicitly provide this in place
using "microseconds{TICKER_TIME}.count()" in the relevant ticker tests.
We recognise this is ugly, but thought it best to descriptively convert
from std::chrono to the host test's required representation.

Co-authored-by: Hari Limaye <hari.limaye@arm.com>

CMake: unittests: Show all tests in CTest report ...

Previously a test executable was recognised as a single test by CTest.
However, test executables usually contain multiple test cases, the
results of the test cases should be individually reported. With our
previous setup we could miss test case failures that didn't cause the
executable to return an error code.

This commit uses gtest_discover_test to discover all test cases in a
test executable. This enables CTest to match test passes and failures
from the googletest binary output.

CMake: unittests: Remove trailing whitespace

Greentea: Remove unused variable from ticker test ...

Ticker test contains definition of variable total_ticks, which is unused
in the file since removal of function wait_and_print() in commit
aaa15bc

Merge pull request #14805 from rkotan/I2C_Multiple_Buses_fix ...

i2c: fix issue #14735 with multiple buses

Merge pull request #14688 from MubeenHCLite/CAN_rxinterrupt_fix ...

Solution for mutex problem in CAN read ISR

Corrected the conditional compilation of RawCAN.

Merge pull request #14881 from jeromecoutant/PR_LED1 ...

Standard Pin Name: LED1 issue for targets without LED

Indentation set for the comments

Remove `#ifdef UNITTEST` from MbedCRC.h ...

Production code should not contain any test-specific checks. Rather
than checking `UNITTEST`, MbedCRC.h can simply include in all cases
<mstd_type_traits> whose unit test stub exists.

Also remove the `UNITTEST` macro from CMake definitions of kvstore
unit tests which depend on MbedCRC.h.

generic_tests update for targets without LED1

Added documentation for the implementation

Spell check corrected

Resolved review comments

Resolving the astyle error

Updated the Licenses for RawCAN and aligned indentation

Added a newline at the end of RawCAN.cpp

Removed the new line at the end of file.

Merge pull request #14828 from hazzlim/add-cmake-supports-psa-tests ...

CMake: Add CMake to mbed-psa greentea tests

Merge branch 'master' into CAN_rxinterrupt_fix

CMake: Require TEST_SOURCES in greentea CMake file ...

Assumption that greentea test file is always named main.cpp is
incorrect. Updated mbed_greentea_add_test() macro to make TEST_SOURCES
parameter compulsory, which is used to specify greentea test
file(s). This allows tests to use C, or have a different name.
Therefore also updated all pre-existing greentea test CMake files to
explicity add main.cpp to TEST_SOURCES.

Added Raw CAN (unlocked can read api) and updated the code for the ...

rxInterrupt to work for all CAN instances

Merge pull request #14786 from ARMmbed/move_drivers_stub ...

Move mbed-stubs-drivers to the drivers directory

CMake: unit-tests: Make drivers stub only depend on headers it uses ...

Previously the drivers stub library depended on `mbed-headers`, which
is a collection of all available headers in mbed-os. To make it easier
to separate the library, only depend on the headers we're using.

CMake: unit-tests: Move mbed-headers-drivers to the drivers directory ...

Move the header-only mbed-headers-drivers library the unit test stubs
depend on into the drivers component directory. This makes the drivers
stubs more self-contained and improves the composition of the library.