feat(wallets): add TON Connect wallet option (Chain.Ton + Jettons)

[GiMa-SwapKit]

Summary

Adds TON Connect as a wallet option, exported as @swapkit/wallets/tonconnect. TON Connect is the standard wallet connection protocol for the TON blockchain and supports only Chain.Ton, including the native token and Jettons.

Implementation

• Follows the Xaman pattern (single-chain, remote-signing protocol): createWallet wrapper in packages/wallets/src/tonconnect/ with supportedChains: [Chain.Ton] and directSigningSupport: { [Chain.Ton]: true }.
• Wraps @tonconnect/ui v3 for the connect modal, universal links, and bridge sessions. Connection uses openModal + onStatusChange (the connectWallet helper is deprecated in v3), detects user cancellation via the modal's action-cancelled close reason, and supports session restore via connectionRestored. An existing TonConnectUI instance can be injected for apps already using @tonconnect/ui-react; otherwise one is created from manifestUrl.
• Delegates message building (native TON and Jetton transfers), balances, and fee estimation to the signerless @swapkit/toolboxes/ton toolbox via createTransaction({ sender }). Signing and broadcasting are routed through the connected wallet's sendTransaction; the returned hash is the external-message cell hash, identical to what toolbox.broadcastTransaction returns.
• Mainnet is enforced via setConnectionNetwork(CHAIN.MAINNET) plus a post-connect check that disconnects testnet wallets.
• Registered in loadWallet, SKWallets, and the supported-chains map; ./tonconnect subpath export added (the builder picks entrypoints up from package.json exports automatically). Changeset included.

Protocol constraints

• Message addresses are normalized to TEP-2 user-friendly form (wallets reject raw 0:<hex>); the connected account's raw address is converted to non-bounceable UQ….
• TON Connect messages carry no sendMode (the wallet chooses it), so sweep transactions (CARRY_ALL_REMAINING_BALANCE) are rejected with a clear error.
• Detached signing (sign) is not part of the protocol and throws; use signAndBroadcastTransaction / transfer.

⚠️ Depends on swapkit/sdk release

CI will show 5 type errors until the SDK side ships — this is expected:

1. @swapkit/helpers: one-line addition to the WalletOption enum: TON_CONNECT = "TON_CONNECT",
2. @swapkit/toolboxes: a release exposing the ./ton subpath (the recently added TON toolbox)

Once released, both versions get bumped in packages/wallets/package.json and CI goes green. Verified locally against patched copies simulating that state: bun tsc --noEmit clean, biome clean, package builds with the new entry.

Usage

connectTonConnect([Chain.Ton], {
  manifestUrl: "https://yourapp.com/tonconnect-manifest.json",
});