fix: cp-7.54.0 use navigation.dispatch to properly navigate to asset page (MetaMask#18461)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**
The 'i' button in the asset row behaves inconsistently depending on the
entry point:
- When accessed from the main action menu, it works as expected.
- When accessed from the token details page, it does not work.

This PR fixes this issue by replacing `navigation.navigate` with
`navigation.dispatch`, which allows the new asset overlay to properly
render as new instead of returning to the previous asset.


<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry:

## **Related issues**

Fixes:

## **Manual testing steps**

```gherkin
Feature: fixed asset page navigation from bridge

  Scenario: user clicks "i" icon from bridge destination token selector
    Given in swap page accessed from asset page

    When user clicks "i" icon
    Then asset page opens for that asset
```

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [ ] 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).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] 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.

## **Pre-merge reviewer checklist**

- [ ] 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.

Author: bfullam

app/components/UI/Bridge/components/BridgeDestTokenSelector/BridgeDestTokenSelector.test.tsx

@@ -15,12 +15,14 @@ import { BridgeViewMode } from '../../types';
 
 const mockNavigate = jest.fn();
 const mockGoBack = jest.fn();
+const mockDispatch = jest.fn();
 
 jest.mock('@react-navigation/native', () => ({
   ...jest.requireActual('@react-navigation/native'),
   useNavigation: () => ({
     navigate: mockNavigate,
     goBack: mockGoBack,
+    dispatch: mockDispatch,
   }),
 }));
 
@@ -164,19 +166,25 @@ describe('BridgeDestTokenSelector', () => {
     // Press the info button
     fireEvent.press(infoButton);
 
-    // Verify navigation to Asset screen with the correct token params
-    expect(mockNavigate).toHaveBeenCalledWith(
-      'Asset',
+    // Verify navigation to Asset screen with the correct token params via dispatch
+    expect(mockDispatch).toHaveBeenCalledWith(
       expect.objectContaining({
-        address: ethToken2Address,
-        balance: '2.0',
-        balanceFiat: '$200000',
-        chainId: '0x1',
-        decimals: 18,
-        image: 'https://token2.com/logo.png',
-        name: 'Hello Token',
-        symbol: 'HELLO',
-        tokenFiatAmount: 200000,
+        type: 'NAVIGATE',
+        payload: expect.objectContaining({
+          name: 'Asset',
+          key: expect.stringMatching(/^Asset-.*-\d+$/), // Should match pattern "Asset-{address}-{chainId}-{timestamp}"
+          params: expect.objectContaining({
+            address: ethToken2Address,
+            balance: '2.0',
+            balanceFiat: '$200000',
+            chainId: '0x1',
+            decimals: 18,
+            image: 'https://token2.com/logo.png',
+            name: 'Hello Token',
+            symbol: 'HELLO',
+            tokenFiatAmount: 200000,
+          }),
+        }),
       }),
     );
   });

app/components/UI/Bridge/components/BridgeDestTokenSelector/index.tsx

@@ -68,8 +68,17 @@ export const BridgeDestTokenSelector: React.FC = () => {
       }
 
       // Open the asset details screen as a bottom sheet
-      const handleInfoButtonPress = () =>
-        navigation.navigate('Asset', { ...item });
+      // Use dispatch with unique key to force new modal instance
+      const handleInfoButtonPress = () => {
+        navigation.dispatch({
+          type: 'NAVIGATE',
+          payload: {
+            name: 'Asset',
+            key: `Asset-${item.address}-${item.chainId}-${Date.now()}`,
+            params: { ...item },
+          },
+        });
+      };
 
       // If the user hasn't added the network, it won't be in the networkConfigurations object
       // So we use the PopularList to get the network name