fix: cp-7.58.0 gasless transaction submission method selection logic

[rarquevaux]

Description

Fixes issue #21613

This PR is a follow-up fix on #21604

Feature: gasless transaction
  Scenario: successful gasless transaction with 7702 on network without sendBundle support
    Given user with smart account for the network and smart transaction off
    When user submit a gasless transaction
    Then the transaction is sent via relay and is successful

  Scenario: cancelled gasless transaction on network without sendBundle support
    Given user with smart account for the network and smart transaction on
    When user submit a gasless transaction
    Then the transaction is sent via smartTransaction submission and is cancelled

Changelog

CHANGELOG entry:

null

Fixes:

Manual testing steps

https://docs.google.com/spreadsheets/d/1m0xBMr48fXhfuOFnzgm9xw2QG5L4sUm6r4Hqaun29E4/edit?gid=0#gid=0

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• 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 format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). 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.

---

Note

Gate smart-transaction batching by Sentinel sendBundle support and fall back to external-sign gasless flow; add Sentinel API util and expand tests.

• Confirmations Hook (useTransactionConfirm):
  • Integrates isSendBundleSupported via useAsyncResult to determine chain capability.
  • Applies smart-transaction handling only when shouldUseSmartTransaction and chainSupportsSendBundle are true; otherwise uses gasless 7702 path by setting txMeta.isExternalSign when a selectedGasFeeToken exists.
  • Preserves batch transactions for bridge quotes; updates dependencies to include chainSupportsSendBundle.
• Utilities:
  • Adds util/transactions/sentinel-api with getSentinelNetworkFlags, isSendBundleSupported, getSendBundleSupportedChains, and buildUrl (fetches from tx-sentinel service).
• Tests:
  • Mocks useAsyncResult and Sentinel API; wraps confirmations in act.
  • Adds/updates cases for wait-for-result logic, missing metadata, navigation paths, batch transactions, smart vs gasless behavior based on sendBundle support, and undefined chainId handling.

^{Written by Cursor Bugbot for commit 3206f7d. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[rarquevaux]

I have read the CLA Document and I hereby sign the CLA

[vinistevam]

PR looks great. I will add those changes to the Extension PR as well.
Here might help with the coverage to pass the sonar validation.

  it('returns false for chainSupportsSendBundle when chainId is undefined', async () => {
    useTransactionMetadataRequestMock.mockReturnValue({
      id: transactionIdMock,
      chainId: undefined,
    } as unknown as TransactionMeta);

    isSendBundleSupportedMock.mockResolvedValue(true);

    useAsyncResultMock.mockImplementation((fn) => {
      fn();
      return { pending: false, value: false };
    });

    const { result } = renderHook();

    await act(async () => {
      await result.current.onConfirm();
    });

    expect(isSendBundleSupportedMock).not.toHaveBeenCalled();
    expect(onApprovalConfirm).toHaveBeenCalled();
  });

  it('does nothing when transactionMetadata is missing', async () => {
    useTransactionMetadataRequestMock.mockReturnValue(undefined);

    const { result } = renderHook();

    await act(async () => {
      await result.current.onConfirm();
    });

    expect(onApprovalConfirm).not.toHaveBeenCalled();
  });

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
88.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud