Mirrors the deposit-intent pattern (PR #30741) for the withdraw flow so
transfer "between accounts" emits its own toast copy per Figma:

  - In progress: "Transfer in progress" / "This may take a few minutes."
  - Success:     "Transfer complete"     / "{{amount}} added to Money account."
  - Failed:      "Transfer failed"       / "Unable to transfer funds. Try again."

initiateWithdrawal() now pre-generates a client-side batchId and registers
a MoneyAccountWithdrawIntent ("betweenAccounts" by default) before the
addTransactionBatch await, so useMoneyTransactionStatus can resolve the
intent for both deferred in-progress toasts and the synchronous immediate
failure path. The intent is cleared on every terminal status (confirmed,
failed, dropped, cancelled, rejected) and when initiateWithdrawal throws.

…conditionally (MUSD-845)

All transfers out of the Money account share the same Figma toast copy
("Transfer in progress / complete / failed"), so the intent-aware
plumbing added in the previous commit was over-engineered:

  - Drop MoneyAccountWithdrawIntent + the batchId-keyed registry, the
    pre-generated batchId in initiateWithdrawal, and the matching
    get/clear/InitiateWithdrawalOptions exports.
  - Drop WithdrawIntent / WithdrawInProgressParams / WithdrawFailedParams
    and the `destination` param on WithdrawSuccessParams.
  - Rename locale keys to drop the now-redundant `_between_accounts`
    suffix, and remove the unused "moved to {{destination}}" copy.
  - useMoneyTransactionStatus.showFor* maps moneyAccountWithdraw
    straight to the new copy with no intent lookup.

Deposit-intent infrastructure (Convert crypto vs Add mUSD) is unchanged.

…toast (MUSD-845)

The transfer success body now reads "{{amount}} added to {{destination}}."
where destination is the user's currently selected internal account's
display name, resolved at toast time from selectSelectedInternalAccount.
Falls back to "Money account" only when no account name is available.

…nt (MUSD-845)

Previously, the transfer success toast read the destination name from
selectSelectedInternalAccount at toast time. That breaks two ways:

  1. If the user switches accounts between submit and confirmation, the
     toast names the wrong account.
  2. The fallback "Money account" was misleading on a withdraw — funds
     don't return to the Money account, they leave it.

The destination is now derived from the actual on-chain transfer: decode
the recipient from the nested tokenMethodTransfer calldata, look it up
via getMemoizedInternalAccountByAddress, and use the account's display
name. Falls back to a shortened recipient address when the recipient is
not one of the user's internal accounts (e.g. external send), and to
"your account" only when the nested transfer tx itself is absent.

Replace the hardcoded English fallback "your account" with a
strings('money.toasts.withdraw_fallback_destination') lookup so it gets
translated for non-English users.

…D-845)

The withdraw success toast read the recipient name from internalAccounts[].metadata.name, which stays empty under the multichain-accounts model where the display name lives on the AccountTreeController account group. Renamed accounts therefore fell back to "your account" even though the picker showed the name.

Prefer the account-group name via selectAccountToGroupMap (keyed by account.id), falling back to the internal-account name, then the localized default — matching the Bridge useRecipientDisplayData precedent.