The user is now able to add, delete, and in general manage multiple
wallets on the same instance of Phoenix. Each wallet can have its own
name and avatar. Internally, wallets are indexed by the hash160 of the
wallet's public node id.

The seed file now stores multiple mnemonics.

The PhoenixBusiness object managing the actual node and coroutines is
now stored by a BusinessManager singleton. Data can be accessed safely
from anywhere including the background service workers. Several
businesses can run concurrently, although this can affect performance,
which will be fixed in a later commit.

Preferences are now per wallet and are managed by a DataStoreManager.
A new global preferences datastore has been added for preferences that
are global to the application, and not a given wallet.

Several ambients assuming non-nullable objects have been removed.

The startup and screenlock mechanism have been reworked to handle
multiple wallets. Specifically, a wallet selector screen lets the user picks
a wallet when needed, though there's also a system to load a wallet
automatically when relevant.

The active wallet is displayed in the Settings menu screen, as well as 
the Receive and Send screen (with incoming liquidity or balance for
convenience)

The navigation graph has been reworked and split into several files for
improved readability.

* (ios) Removed obsolete CloseDatabase parameter when stopping business

This parameter was introduced and used only by the Android app because of
long standing issues with the background system, which have been fixed with
the multiple wallets support update.

---------

Co-authored-by: Robbie Hanson <304604+robbiehanson@users.noreply.github.com>

The PhoenixBusiness object is tied to a specific wallet. It can be
destroyed, or many instances can be created. It's not suited for
routines that have application-wide scopes, such as the Currency
Manager.

A PhoenixGlobal class has been created with the expectation
that it's created at application startup, and that it is unique.

The CurrencyManager logic is the same as before, though there
has been some refactoring.

---------

Co-authored-by: Robbie Hanson <304604+robbiehanson@users.noreply.github.com>

Also bumped dependencies (SQLDelight, Okio, and Android libraries).

Note that kotlin 2.2.20 is available, but not supported by SKIE just yet.

The wallet-context resource now contains a boolean to enable or
disable manual liquidity. If disabled, the request liquidity
button is hidden in the UI.

Also fixed a few issues with the `PhoenixGlobal` jobs.

---------

Co-authored-by: Robbie Hanson <304604+robbiehanson@users.noreply.github.com>

This commit upgrades lightning-kmp to v1.11.0, which brings taproot
channels to Phoenix. It also updates kotlin and cleans up legacy code.

Notably, the tools for the legacy channel data backup have been
removed, and the import-channel-data helper can be removed.

The spend-from-channel-address screen has been disabled. The
import-channel-data screen is obsolete and has been removed.

* Use abstract payerKey and payerNote in offer metadata

See ACINQ/lightning-kmp#821

Also limit the description input to 64 chars for Bolt12 offers
as the description + payer note cannot exceed 64 chars.

---------

Co-authored-by: Robbie Hanson <304604+robbiehanson@users.noreply.github.com>

* (ios) Incrementing build number, and aligning upgrade mechanisms (for multi-wallet) with new build number
* (ios) Safety change: don't delete the old security.json file. For now, just move it out of the way.