…every tap (MetaMask#30318)

<!--
Please submit this PR as a draft initially.

Do not mark it as "Ready for review" until this PR meets the canonical
Definition of Ready For Review in `docs/readme/ready-for-review.md`.

In short: the template must be materially complete (not just section
titles
present), all status checks must be currently passing, and the only
expected
follow-up commits must be reviewer-driven.
-->

## **Description**

This branch wires up the existing **`onSelectAccount`** route param on
`AccountSelectorParams` so callers opening the picker via
`createAccountSelectorNavDetails` receive a callback on **every** tap
inside the picker — including taps on the already-selected account.

**Previous behaviour:** The `onSelectAccount` route param was declared
on
[`AccountSelectorParams`](app/components/Views/AccountSelector/AccountSelector.types.ts)
but never invoked anywhere. Consumers that needed to know "the user
committed a selection" had to read Redux state diffs on
`AccountTreeController:selectedAccountGroupChange`, which does not emit
when the user re-taps the already-selected account. Combined with the
fact that both tap-commit and back-out paths end in
`navigation.goBack()`, callers had no signal to distinguish a
same-account commit from a dismiss.

**New behaviour:**

1. **Tap any account (different or same)** —
`_onSelectMultichainAccount` calls `setSelectedAccountGroup` (existing
behavior), then invokes the route param `onSelectAccount(accountGroup)`,
then closes. The callback fires regardless of whether the controller
actually emitted a state change.
2. **Back out / dismiss** — Unchanged: `navigation.goBack()` only;
callback does NOT fire.
3. **No callback provided** — Unchanged: picker behaves identically to
before.

Signature updated from `(address: string) => void` to `(accountGroup:
AccountGroupObject) => void` to match the multichain context. No
production caller passes this route param today (verified via repo-wide
search for `createAccountSelectorNavDetails`), so this is a safe,
additive surface change.

### Why

- Re-tapping the already-selected account inside a generic picker is a
real user signal in flows that have a "virtual" funding source layered
on top of the regular account (e.g. Money Account as Card funding source
on the spending limit screen). Without this callback, consumer screens
have no way to detect it.
- Wiring the existing param keeps the public surface unchanged and
avoids introducing a parallel naming convention.

### What changed (scoped paths)

| Area | Files / behaviour |
| ---- | ----------------- |
| **Picker route param type** |
[`app/components/Views/AccountSelector/AccountSelector.types.ts`](app/components/Views/AccountSelector/AccountSelector.types.ts)
— updated `onSelectAccount` signature to `(accountGroup:
AccountGroupObject) => void` and clarified JSDoc that it fires on every
tap. |
| **Picker wiring** |
[`app/components/Views/AccountSelector/AccountSelector.tsx`](app/components/Views/AccountSelector/AccountSelector.tsx)
— destructure `onSelectAccount` from route params and invoke inside
`_onSelectMultichainAccount` between `setSelectedAccountGroup` and
`handleClose`. |
| **Tests** |
[`app/components/Views/AccountSelector/AccountSelector.test.tsx`](app/components/Views/AccountSelector/AccountSelector.test.tsx)
— 3 new tests: callback fires with the tapped group; callback still
fires when re-tapping the already-selected account; picker does not
throw when the callback is absent. Updated existing mock's signature. |

### Out of scope (intentional)

- Other selector components that have their own component-level
`onSelectAccount` prop (`MultichainAccountSelectorList`,
`AccountListCell`, `AccountConnectSingleSelector`, etc.) — none touched.
- No changes to controllers, messengers, or default picker behavior for
any existing consumer.

## **Changelog**

CHANGELOG entry: Wired the existing `onSelectAccount` route param on the
global Account Selector picker so callers receive a callback on every
account tap (including re-tapping the already-selected account),
enabling consumer screens to distinguish a committed selection from a
dismiss.

## **Related issues**

Fixes:

<!-- Add ticket ID(s), e.g. Fixes: MUSD-xxx or MetaMask#12345 -->

Used by companion PR
[MetaMask#30320](MetaMask#30320) (Card
spending limit) to detect the "user is exiting Money Account mode by
re-tapping the same regular account" case.

## **Manual testing steps**

```gherkin
Feature: Optional onSelectAccount callback on the global Account Selector picker

  Background:
    Given a caller opens the Account Selector via createAccountSelectorNavDetails
    And the user has more than one account group

  Scenario: caller passes onSelectAccount and the user taps a different account
    When the user taps an account group different from the current one
    Then the picker calls setSelectedAccountGroup with the tapped group's id
    And the onSelectAccount callback is invoked with the tapped account group
    And the picker closes

  Scenario: caller passes onSelectAccount and the user re-taps the already-selected account
    When the user taps the account group that is already selected
    Then setSelectedAccountGroup is still called (no state change emitted)
    And the onSelectAccount callback is invoked with the tapped account group
    And the picker closes

  Scenario: caller passes onSelectAccount and the user dismisses without picking
    When the user taps the back arrow / swipes the picker down
    Then the onSelectAccount callback is NOT invoked
    And the picker closes

  Scenario: caller does NOT pass onSelectAccount (existing flows)
    Given the caller opens the picker without the onSelectAccount route param
    When the user taps any account
    Then the picker behaves identically to before (setSelectedAccountGroup + close)
    And no error is thrown
```

## **Screenshots/Recordings**

### **Before**

<!-- No visual change; behavioural only. Existing consumers (Wallet tab,
etc.) unaffected. -->

### **After**

<!-- Same picker UI. Consumers that opt in via the route param now
receive a tap signal. -->

## **Pre-merge author checklist**

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [ ] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [ ] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [ ] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Changes the Account Selector navigation contract by invoking an
optional route callback on selection and altering its signature to pass
an `AccountGroupObject`, which could impact any existing callers and
selection flow ordering.
> 
> **Overview**
> **Account Selector now invokes an optional `onSelectAccount` route
param on every account tap.** `AccountSelector` wires
`route.params.onSelectAccount` into `_onSelectMultichainAccount`,
calling it *after* `AccountTreeController.setSelectedAccountGroup` and
*before* closing the sheet, so callers get a commit signal even when
re-tapping the already-selected account.
> 
> **API and tests updated.** `AccountSelectorParams.onSelectAccount` now
receives an `AccountGroupObject` (instead of an address string) with
updated JSDoc, and `AccountSelector.test.tsx` adds coverage for callback
firing (same/different account), ordering vs `goBack`, non-callback
behavior, dismiss via back arrow, reload flag reset, and sub-screen back
navigation.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
ad94198. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->