[BH-1866] Port new eMMC driver to Pure

This port updates only the eMMC driver and
a few files from new FSL. This change
should solve an issue with init eMMC memory.

[BH-1787] Reboot to MSC endpoint

To allow the automation of gathering logs and swapping out OS images during tests a MSC reboot
endpoint was added. Together with a change to ecoboot, this allows the sending of a "reboot to
MSC" command. The deivce will then reboot and enter MSC mode.

[BH-1814] Fix eink errors in logs

According to the newest fsl library the LPSPI_Reset function
shouldn't be invoked in LPSPI_MasterInit function.
As a result, the LPSPI module can't work after calling this API.

If the display returns the error the driver could invoke
EinkPowerDown function recursively which causes a crash.

[BH-1688] Create a standard for logs

* Adding document describing how to use logger
* Adjusting logs to follow a new guide
* Change order in log header:
  line number is now before function name

[MOS-669] Add too hot battery notification when charging

* Added notification showing on the main
screen if the battery has reached too
high temperature to continue charging.
* Code cleanups.

[MOS-1011] Fix frequency switching stability

Multiple fixes of clock switching related
stability issues:
* added RC oscillator hysteresis as in NXP example;
* changed DCDC converter config;
* configure PLL2 to be able to run on any CPU
frequency level;
* added switching to 1.275V (overdrive) voltage
when applying any clock change above 12MHz as
well as LDO or bandgap switching, as done in
Mbed OS' lpm.c for RT1050;
* changed BMCR AXI queues weighs for SDRAM
in JLink scripts to disable operations
reordering, as it is known to cause data
integrity issues;
* extracted some code to separate files;
* smaller or bigger code cleanups.

[MOS-1026] Add extended logging to Pure's charger driver

* Added extended logging to Pure's charger driver.
* Removed redundant handling of INOKB pin
interrupt - charger is configured to provide
the same interrupt via INTB pin.
* Minor code cleanup.

[MOS-1018] ServiceAudio power management optimizations

Optimized power management strategy used by
ServiceAudio:
* changed minimum CPU frequency from 528MHz to 264MHz;
* added switching to 24MHz when operation active,
but paused;
* minor cleanup in several places.

[MOS-1014] Screen remains black after turning off the phone with dark mode enabled

Regression fixed by adjusting wipeout function.

[BH-1412] Whitelist update

Whitelist removed for Harmony
Changed the way whitelist is obtained
Added missing logs for Eink Dispaly

[MOS-1012] Fix occasional crash when unplugging Pure from PC

Fix of the unhandled error issue that resulted
in occasional device crash when disconnecting
from PC with MC app running.

[BH-1714] Handling eink initialization errors

Added error detection while eink initialization.
Added mechanism to reinitialize the eink in case of error.

[BH-1714] Eink refactor and error handling

Cleanup and refactor for eink code.
Changed turning on/off procedure.
Add error handling.

[BH-1730] Fix enter into SNVS mode

If the CPU fails during changing the frequency
the device can stuck in SNVS mode.
So the CPU frequency is checked and if
the frequency is wrong the CPU doesn’t enter SNVS mode.
The watchdog should restart the CPU.

[MOS-599] Fix undefined phone mode in simulator

Fix of the issue that on simulator phone mode
was in 'undefined' state, what resulted in
no phone mode selected in settings.

[MOS-998] Provide additional info in crashdump filename

Added info about product, OS version and
commit hash to crashdump filename to
simplify analysis of the crashdumps
without corresponding logs available.

[BH-1717] Fix no clock update

The secure RTC can lock and the clock is not updated.
To prevent this situation we reset LP registers (except for
timestamps and alarms) and clear the LVD flag. Then we
enable again LP SRTC.

[MOS-997] Fix failing sync with Mudita Center

Fix of the issue that sync with Mudita Center
would fail often after changes introduced in
CP-1968.

[BH-1708] Fix buttons behavior

When the button is pressed/released we get an interrupt
which falls or rises edge. We read the gpio state a bit
later so in case of debouncing we can register
the wrong pin state.
After the debounce interval the state is stable.

[BH-1718] Add extra logs to the RTC module

Add extra logs when the RTC timeout error occurs.
In that, we can find reason in registers of what happened.