Validate intent typedData in bridge quote responses

[oscarwroche]

Explanation

• Extend bridge quote validation to accept intent.typedData for intent swaps.
• Keep validation lightweight for typedData.domain and typedData.message to avoid deep type recursion while still checking structural EIP‑712 fields.

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
• 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
Medium risk because it changes intent-order submission to optionally sign EIP-712 data via KeyringController, affecting transaction submission behavior and introducing a new failure mode when typedData is absent.

Overview
Intent quote validation now accepts optional EIP-712 intent.typedData payloads (lightweight structural checks for required fields) when validating bridge quote responses.

BridgeStatusController.submitIntent now treats signature as optional: if omitted, it signs the provided intent.typedData internally via KeyringController:signTypedMessage (V4); if both signature and typedData are missing it throws. Updates messenger action typings accordingly and adds unit tests covering the autosign + missing-data error paths.

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