Refactor KVStore config override explanation ...

The documentation previously referred to a weakly defined function
`storage_configuration`, however, this function was replaced at some
stage by `kv_init_storage_config`. Refactor the explanation on how to
override the default configurations to reflect this. Also, remove
the snippet which was used to show the implentation of
`storage_configuration`.

Deprecate TDB_EXTERNAL_NO_RBP and FILESYSTEM_NO_RBP in kv_config ...

NO_RBP (no rollback protection) is intended to not require an internal
TDB, however, DeviceKey, which we use to derive SecureStore's
encryption key, still does. Currently, no internal TDB is created with
these two configurations, meaning there's no way to store the DeviceKey
and SecureStore doesn't work.

fix(docs): corrects various typos in project documentation

TDBStore Whitebox tests: fix memory check ...

Each block of HeapBlockDevice is only allocated from the heap when
that block is programmed. And erasing a block frees the associated
buffer.

To decide if there is enough heap to run the TDBStore Whitebox tests,
we need to perform a trial program() instead of erase().

TDBStore: call `BlockDevice::erase()` regarless of erase value ...

From the documentations of `BlockDevice::get_erase_value()`:

    -1 if you can't rely on the value of the erased storage

and `BlockDevice::program()`:

    The blocks must have been erased prior to being programmed

So, `BlockDevice::erase()` should always be called regardless of
erase value.

TDBStore: optimize erase algorithms ...

Currently `TDBStore::offset_in_erase_unit()` and
`TDBStore::check_erase_before_write()` loop through erase units
one-by-one, until the entire range is covered. This is very inefficient
when the erase size is tiny, e.g. one-byte on a non-flash device for
which we use program as erase.

This commit reworks the algorithms, based on the fact that a block
device can erase or program as many units as needed in one go.

FileSystemStore unit test: remove erased_set_get test ...

The "erased_set_get" test case deinits `FileSystemStore`, erases the
block device, and reinits `FileSystemStore`. This of course fails,
because `BlockDevice::erase()` removes all stored data including the
format of the `FileSystem` (middle layer), unless the particular type
of block device has a no-op erase implementation.

Note: Previously `HeapBlockDevice::erase()` was essentially a no-op
so this test case did not fail. We recently added the freeing of heap
memory and it uncovered the problem.

HeapBlockDevice::erase(): free up heap memory ...

`HeapBlockDevice::erase()` previously performed a range and alignment
check only. This commit adds freeing of heap memory.

HeapBlockDevice: allocate with std::nothrow ...

Mbed OS does not enable C++ exceptions, so we should call `new` with
`std::nothrow` which returns a C-style NULL pointer when allocation
fails to allow error handling.

For consistency of style within the same file, this commit also
replaces `malloc()` and `free()` to `new (std::nothrow)` and `delete`.

Add standard pin-names validation script & tests

[STD-PIN] update tests and components

Remove: ARM_MUSCA_A1 support ...

ARM_MUSCA_A1 is not supported since Mbed OS 6.0
Refer: https://github.com/ARMmbed/mbed-os/pull/13165

Therefore remove files from kv_config and TF-M post binary hook script.

Merge pull request #14031 from arduino/blockdevices_namespaces ...

BlockDevices: specify mbed namespace where needed

CMake: rename greentea test macro

fix namespaces for MBED_NO_GLOBAL_USING_DIRECTIVE feature ...

added namespaces in various files

BlockDevices: specify mbed namespace where needed

Merge pull request #14137 from rajkan01/fix_fatfilesytem_unmount ...

Storage: Fix FATFileSystem unmount issue

Merge pull request #14063 from dustin-crossman/pr/wifi_reserved_region ...

Support arbitrary storage alongside WiFi firmware in external storage on Cypress targets

f_mount() (http://www.elm-chan.org/fsw/ff/00index_e.html - third party libary) API is called from both mount() and unmount() Mbed OS APIs. ...

f_mount() is doing both initializing (via find_volume() -> disk_initialize() where disk_initialize api calls Mbed OS init() function)
underlying block device and register filesystem but in case of "unmount" calls this f_mount is doing deregister filesystem
and missed to a deinitializing block device. So added the Mbed OS "deint()" call in unmount API to deinitialize block device
as f_mount API doesn't have a way to call deinit().

CMake: Add support for Filesystem Greentea tests ...

The Filesystem Greentea tests can now be built with CMake

Merge pull request #14090 from hugueskamba/hk_cmake_greentea_blockdevice ...

CMake: Add support for Blockdevice Greentea tests

Merge pull request #14088 from hugueskamba/hk_cmake_greentea_kvstore ...

CMake: Add support for KVstore Greentea tests

Merge pull request #14078 from hugueskamba/hk_rename_ospif_include_dir ...

CMake: Add support for OSPIF blockdevice

CMake: Add support for Blockdevice Greentea tests ...

The Blockdevice Greentea tests can now be built with CMake

CMake: Add support for KVstore Greentea tests ...

The KVstore Greentea tests can now be built with CMake

CMake: Add Blockdevice dependency to KVstore library ...

As KVstore relies on BlockDevice add the dependency
in Mbed OS so applications do not have to specify it

CMake: Add support for OSPIF blockdevice

Correct OSPIF include directory ...

The include directory was incorrectly named QSPIF.

Merge pull request #14036 from ahmetalincak/maxim-max32630fthr-SD-configuration ...

Add SD component and Update SD card SPI interface for Maxim's MAX32630FTHR

Merge pull request #14065 from hugueskamba/hk_cmake_streamline_kvstore ...

CMake: streamline kvstore support