Feat/add stellar bridge status controller

[Julink-eth]

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
• 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
Introduces a new non-EVM chain path (Stellar) affecting quote validation, CAIP asset parsing, snap transaction submission, and polling/metrics logic; incorrect chain/asset detection or polling conditions could break swaps or status tracking for Stellar flows.

Overview
Adds Stellar (XLM) network support across the bridge stack: Stellar is now treated as a supported non-EVM chain (new ChainId.STELLAR, XlmScope.Pubnet, default native token metadata, and updated chain ranking/allowed chain IDs), and isStellarChainId is exported for downstream consumers.

Extends CAIP/asset formatting to handle Stellar-specific asset identifiers, including classic CODE-ISSUER assets (asset:) and Soroban contract IDs (sep41:), and updates quote validation/tests and non-EVM fee handling to cover Stellar quote flows.

Updates BridgeStatusController to submit Stellar swaps via snap signAndSendTransaction and to poll for Stellar status (treating Stellar similarly to bridge/intent/tron for polling and avoiding premature “Completed” tracking), with comprehensive new unit tests and changelog entries.

^{Reviewed by Cursor Bugbot for commit 1b7363a. Bugbot is set up for automated code reviews on this repo. Configure here.}