Files are removed separately to the initial simulator commit in
order to make it clearer what has been changed.

The simulator uses emscripten to run in the browser, meaning that
the nRF hardware API can no longer be used. Though the mbed API
along with its HAL is reimplemented using emscripten and
javascript. Instead of plugging into hardware, EM_ASM is used at
points to call directly into javascript.
Persistent memory is also removed and replaced with local
javascript memory.
Inline assembly is no longer supported.
Due to javascript being single threaded, in order to yield to the
browser and "hardware" threads, mp_hal_delay_ms is used to call
emscripten_sleep in the VM and throughout.
The initial stack usage is simulated by initialising the stack top
using a dummy value at the start of main.
Javascript is used in order to import any MicroPython script from
the simulator web page that exists on soft reset.
The stack may ascend on the machine running the browser and so the
stack_usage now accounts for that.
The yielding within the VM uses a counter to periodically check
whether enough time has passed for it to yield yet, this time
checking prevents fast CPUs yielding to the browser more frequently
than necessary.

The nRF API is partially implemented in order to support the ticker,
with most methods being stubbed out. The ticker is implemented using
a javascript timeout function that calls the handler. Due to the
unreliability of javascript's timing, the handler is called more
frequently than is necessary for the slow ticker, and the time that
has passed is checked.
The nrf_gpio API calls directly into mbed's gpio API.
Implementing the pin API allows the display to run, though the light
sensor is not yet implemented.

Asyncify seems to prevent ccalls such as the ticker during emscripten_sleep.
To get around this issue, only briefly call emscripten_sleep in mp_hal_delay_ms,
and check ticks passed to return at correct time.

Explicitly handle exceptions.

…andom memory.

…ns from Python.