Add transfer UI to send assets to another account (fallback when external tools fail)

[temptemp3]

Summary

Add an in-app transfer flow so users can send tokens / assets to another account from the Humble interface. This serves as a reliable fallback when wallets, explorers, or other transfer tools are unavailable or misbehaving.

Motivation

• Users still need to move funds for trading, LP, or personal transfers; when third-party tooling breaks, the interface should offer a basic, trustworthy path.
• Reduces support burden and improves resilience of the overall UX.

Scope (suggested)

• Support native and ASA / ARC-200 (or whatever the app already lists) transfers consistent with existing network support.
• Clear recipient address input with validation (checksum / format).
• Amount entry with balance hint and decimals handling.
• Review + confirm step before signing (wallet-driven signing as today).

Non-goals

• Replacing full wallet functionality; this is a focused transfer helper, not a general wallet.

Acceptance criteria

• User can initiate a transfer from the UI to a destination address for supported asset types.
• Amount cannot exceed spendable balance; errors are understandable.
• Transaction is built and passed to the connected wallet for signing (or app pattern used elsewhere).
• Copy clarifies this is a standard transfer, not a swap or pool action.

Open questions

• Entry point: global Send / Transfer action vs. per-asset menu in wallet/balance views?
• Networks: Voi only, Algorand only, or both—align with product scope.

Notes

Phrase as fallback in user-facing copy only if desired; primary framing can simply be “Transfer” to avoid sounding negative.