Break mbed-drivers dependency

If we want to remove dependency on mbed-drivers. I had a quick look at files within hal, which are referenced within hal tree:

Files from mbed-drivers used in target's HAL:
- pinmap common (uses error() if pinmap not found)
- mbed error (mbed_die() -> which requires wait_us)
- mbed assert - exit() and mbed_die()
- us ticker api

All these are currently in mbed-drivers module. There are some dependencies on other files as highlighted above. Thus to have HAL not depend on mbed-drivers, we would need to move files above, plus this additional files:
- error
- exit
- mbed_assert (use from core-util which depends on mbed-drivers)
- mbed_die
- mbed_interface - weak mac address (needs to be fixed)
- wait

@bogdanm @bremoran @salkinium

Start by auditing the files within the hal tree and the listed mbed-drivers references: pinmap common, mbed error, mbed assert, us ticker api, error, exit, mbed_assert, mbed_die, mbed_interface, and wait. Trace their dependencies, including core-util and wait_us, then verify that the HAL no longer depends on mbed-drivers and that the weak MAC address issue is addressed.

Written by the indexing model from the issue text.