feat!: (wip) use crosschain api instead of intent manager for intent order submission

[oscarwroche]

Explanation

References

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, highlighting breaking changes as necessary
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

---

Note

Replaces IntentManager with a new CrossChain API client for submitting and polling intent orders, adds intent order types/status mapping, and updates history/metrics handling accordingly.

• BridgeStatusController:
  • Replace @metamask/intent-manager with CrossChain API integration via new IntentApiImpl (submitIntent, getOrderStatus).
  • Update intent polling to fetch status with IntentApiImpl.getOrderStatus using orderId, aggregatorId, and chainId (as strings); remove IntentManager field/setter.
  • Map intent provider statuses (IntentOrderStatus) to TransactionStatus and update corresponding TransactionController entries; merge tx receipts/hashes when available.
  • Maintain intent history entries using intent:-prefixed IDs; consolidate tx hashes from txHash and metadata.txHashes.
  • Minor parameter/data tweaks: use srcChainId.toString(), pass quoteId/order in submission, keep originalTransactionId for syncing.
• New types/files:
  • Add intent-api.ts (API client), intent-order-status.ts (status enum), and intent-order.ts (order shape).
• Changelog:
  • Mark breaking change: use CrossChain API instead of intent manager for intent order submission.

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