feat(transaction-pay): add ordered strategy fallback orchestration

[pedronfigueiredo]

Explanation

As per preemptive validation on #7806

• Adds ordered strategy retrieval via TransactionPayController:getStrategies while preserving existing getStrategy behavior.
• Adds compatibility filtering (supports(...)) during strategy selection.
• Implements quote fallback orchestration:
  • try next strategy when quote retrieval fails
  • try next strategy when quote list is empty
  • skip unsupported strategies
• Implements publish-hook fallback orchestration:
  • execute primary strategy from existing quote strategy
  • on execution failure, rebuild quote requests and try next compatible strategy
  • throw original primary error if all fallback attempts fail

References

Addresses https://github.com/MetaMask/MetaMask-planning/issues/6992

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Medium Risk
Changes core quote retrieval and publish-path strategy selection; failures in ordering/validation or supports logic could lead to missing quotes or executing an unintended strategy.

Overview
Adds ordered pay-strategy orchestration for quote retrieval: TransactionPayController can now accept a getStrategies callback (or remote feature flag strategyOrder) and updateQuotes/refreshQuotes iterate strategies in order, skipping unsupported ones (supports) and falling back when quote/batch-tx retrieval fails or returns empty.

Strategy selection is hardened by validating strategy names (isTransactionPayStrategy), adding getStrategiesByName to resolve/skip unknown strategies, and changing the publish hook to execute the strategy encoded in the stored quote (quotes[0].strategy) rather than re-selecting at publish time. Docs/changelog and tests are updated accordingly.

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

[cursor]

Source amounts strategy mismatch with fallback strategy selection

Medium Severity

The updateSourceAmounts call in #updateTransactionData uses getStrategy (returning the first strategy) to decide whether same-token quotes are required via isQuoteAlwaysRequired. But the new fallback loop in getQuotes may select a different strategy. For a Hyperliquid USDC deposit where the payment token matches the required token, if Bridge is first in the order, isQuoteAlwaysRequired returns false, the source amount is skipped, and no quote requests are built — so even when Relay (which does need that quote) is tried as fallback, requests is already empty and getQuotes returns early with no quotes.

Additional Locations (1)

• packages/transaction-pay-controller/src/TransactionPayController.ts#L159-L174