feat(transaction-pay-controller): add route-based strategy resolution

[pedronfigueiredo]

Explanation

This change moves the generic confirmations_pay strategy-order routing logic into @metamask/transaction-pay-controller so clients no longer need to own the raw feature-flag parsing and ordered strategy resolution themselves.

References

• Related to refactor: split mm pay ui type cleanup into follow-up pr metamask-mobile#27867
• Consumer follow-up branch: pnf/plan-provider-fallback-rollout

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 how TransactionPayController chooses fallback pay strategies by adding route-aware feature-flag parsing (chain/token/transactionType overrides) and enabled-strategy filtering, which can alter quote/submit behavior across transactions. Risk is mitigated by extensive unit tests but impacts core payment routing.

Overview
Adds route-aware pay-strategy resolution inside @metamask/transaction-pay-controller. When custom getStrategy/getStrategies callbacks don’t return a valid strategy, the controller now resolves an ordered strategy list from confirmations_pay using route context (payment token chainId/address + transaction.type).

getStrategyOrder is expanded to normalize and validate override configs, apply a clear precedence (transaction-type + token/chain overrides down to global defaults), and filter out disabled strategies; a new getStrategy helper returns the first applicable strategy. Tests are updated/expanded to cover routing precedence, case normalization, disabled-strategy behavior, and to assert internal raw-flag helpers are not exposed, and the changelog notes the new route-based resolution.

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

[matthewwalsh0]

As in the transaction controller, the intent of these utils is to abstract the feature flag schema to retrieve values based on relevant args.

So we don't want to expose the raw values, but instead return the relevant data, so we could just have getStrategy(chainId, tokenAddress, transactionType) for example?

[matthewwalsh0]

No change?

[pedronfigueiredo]

I added the suggested util getStrategy and getStrategyOrder

[matthewwalsh0]

What is the purpose of this file? Are we just trying to accomodate the localOverrides?

Do they even function for JSON flags?

Could this just go inside feature-flags.ts?

[matthewwalsh0]

Do we not still need to call our new routing if neither of these is defined?

[pedronfigueiredo]

Yes, getStrategy and getStrategies come from the client overrides, but we still want to fallback to the feature flag configured values in the client. I added the missing arguments

[matthewwalsh0]

This can still be done internally, but as a fallback if the client hasn't explicitly provided their own strategy logic via one of the two callbacks?

[matthewwalsh0]

No change?

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}