[skip ci]

[skip ci]

Every device now has its own context, which contains everything a
device might need. Type-specific traits are implemented on the
context and not the state itself (e.g., QmiDevice is implemented for
QmiBundle, which is a QRTR-specific state context paired with a common
QMI state context). A state context is now basically a mutex-like object
allowing exclusive access to the state with a few bonus features such as
actions and D-Bus updates.

This makes it easier to call type-specific methods on a device while
keeping a mutable shared device state.

QMI NoEffect errors are ignored now because they don't necessarily mean
something has failed.

Network management only works on platforms with bam-dmux, IPA is not
supported yet because it requires multiplexing via QMAP.

The device handle is now managed as part of the state, allowing actions
to modify it (e.g. allocate new QMI clients). In the future, all
device interactions will go through the state and the handle won't be
passed around at all.

Multithreading has been disabled due to the use of locking in the QRTR driver
in Linux, which seems to cause some multithreaded socket operations to hang.

The code was copy-pasted from the NAS init sequence and I forgot to
change the message type from NAS to Voice.

Currently supported: attach state, operator name, roaming status
To be done: signal strength, data capabilities

This seems to fix a deadlock that occurs when an indication updating
the slot state is received during an action.

The event type is no longer exposed to device modules. Instead, the
events are all sent through the state context, which now has its own
module.

Events and actions are now processed asynchronously inside separate
Tokio tasks.

Two new actions have been implemented, which allow users to activate and
deactivate SIM cards.

[skip ci]