This ringbuffer-based approach was the original implementation before we
had a way to support running events synchronously from the BLE stack.

Zephyr is the last remaining port using this. ESP32 no longer requires it
as of 5dbb822 & e05d0a6. The Zephyr BLE support is about to be updated
anyway.

This commit also removes the MICROPY_PY_BLUETOOTH_ENTER/EXIT guards. This
was previously a no-op on ports using sync events (e.g. stm32). Replaced
with MICROPY_BEGIN_ATOMIC_SECTION where necessary it was used in other
locations (e.g. unix mpbthciport.c).

Also makes pairing & bonding enabled by default (this was effectively the
current behavior as it was enabled when sync events were enabled).

This work was funded through GitHub Sponsors.

Signed-off-by: Jim Mussared <jim.mussared@gmail.com>

Also provide a no-op mutex when threading is disabled.

This work was funded through GitHub Sponsors.

Signed-off-by: Jim Mussared <jim.mussared@gmail.com>

This work was funded through GitHub Sponsors.

Signed-off-by: Jim Mussared <jim.mussared@gmail.com>

This abstracts the implementation currently used by modbluetooth.c
to get BLE events from the host stack running in an RTOS task into
a MicroPython task.

This existing implementation only works when the GIL is enabled, so also
add a scheduler-based implementation for non-GIL ports (e.g. Unix).

This work was funded through GitHub Sponsors.

Signed-off-by: Jim Mussared <jim.mussared@gmail.com>

This replaces the bluetooth-specific implementation previously enabled when
MICROPY_PY_BLUETOOTH_USE_SYNC_EVENTS_WITH_INTERLOCK was enabled to
synchronously run a host-stack callback on a MicroPython thread.

When MICROPY_PY_THREAD_RTOS is not enabled, this is a no-op and the
call goes directly (e.g. stm32, where the host stack is running in the
scheduler).

Also enables this for esp32 by removing
MICROPY_PY_BLUETOOTH_USE_SYNC_EVENTS_WITH_INTERLOCK and adding
MICROPY_PY_THREAD_RTOS.

This work was funded through GitHub Sponsors.

Signed-off-by: Jim Mussared <jim.mussared@gmail.com>

This provides a full implementation of the NimBLE mutex, critical section,
and semaphore. On ports without threading, this is a no-op change, but this
is necessary to make NimBLE's locking functionality work on threaded ports.

This work was funded through GitHub Sponsors.

Signed-off-by: Jim Mussared <jim.mussared@gmail.com>

MICROPY_EVENT_POLL_HOOK should bounce the GIL like other ports.

This work was funded through GitHub Sponsors.

Signed-off-by: Jim Mussared <jim.mussared@gmail.com>

This replaces the previous code that used the scheduler (via thread) to
run the BLE host stack.

Now the host stack can run directly on the thread, and then
modbluetooth.c will use mp_thread_run_on_mp_thread to run the
Python-level callbacks on a MicroPython thread as necessary.

This work was funded through GitHub Sponsors.

Signed-off-by: Jim Mussared <jim.mussared@gmail.com>

Implement a UART transport:
The way transports worked changed slightly in NimBLE 1.6.0 anyway, but
this allows us to hook the "send payload" directly, rather than having
to go byte-at-a-time via the tx callback. Also implemenets a mutex on
transmission as nothing prevents NimBLE sending both a CMD and ACL
payload at the same time.

Common implementation of mpnimbleport.c for scheduler-based ports:
Makes stm32, renesas-ra, mimxrt, rp2 use a shared implementation.

Simplify the NPL event queue:
We only need to process the single default queue, so remove the
additional logic to handle the linked list of queues. Also rename the
functions to execute the queues and run timers.

Unix:
Implement the HCI layer more like an RTOS port, where you have a task
running the host stack, and UART data is sent directly to NimBLE from
a UART IRQ. This makes it behave more like ESP32 or Zephyr, where we
only run the Python-level callbacks in a MicroPython thread.

This work was funded through GitHub Sponsors.

Signed-off-by: Jim Mussared <jim.mussared@gmail.com>

For _IRQ_GATTC_READ_DONE, we should wait for it to ensure that we receive
it before we sent the write (this prevents an ordering race with the
"gattc_write" vs the "_IRQ_GATTC_READ_DONE" line).

For _IRQ_GATTC_WRITE_DONE, don't print it out because we wait for it anyway
(so it will be confirmed to have been generated), and it can race with
the concurrent notify or indicate event.

This work was funded through GitHub Sponsors.

Signed-off-by: Jim Mussared <jim.mussared@gmail.com>

Filter out escape sequences to set the color. Also allow the "TX:" and
"RX:" used in some places.

This work was funded through GitHub Sponsors.

Signed-off-by: Jim Mussared <jim.mussared@gmail.com>