fix: handle non-url origins

[0xEdouardEth]

Explanation

This PR updates the Stellar Snap confirmation origin helpers to handle non-URL origins such as the stable wallet-connect origin used by MetaMask Mobile WalletConnect multichain requests.

Valid HTTP(S) URL origins continue to be displayed as hostnames. Known non-URL origins are displayed with friendly labels, currently MetaMask and WalletConnect. Unknown invalid origins, including WalletConnect channel IDs, now format to an empty string so confirmation UI can avoid showing meaningless identifiers.

Tests were added for known origins, URL origins, non-http URLs, WalletConnect channel IDs, invalid origin strings, and the existing confirmation utility behavior.

References

• Related to MetaMask Mobile PR: refactor(walletconnect): use stable origin for Tron snap requests metamask-mobile#32339
• Related Tron Snap PR: fix: handle non-url origins snap-tron-wallet#340

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
  • N/A - no package changelog update needed for this internal behavior fix.
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them
  • N/A - this does not introduce a breaking API change.

Validation

ENVIRONMENT=test LOG_LEVEL=error ... yarn workspace @metamask/stellar-wallet-snap jest packages/snap/src/ui/confirmation/utils.test.ts --runInBand --coverage=false

Result: 1 test suite passed, 23 tests passed.

yarn eslint packages/snap/src/ui/confirmation/utils.ts packages/snap/src/ui/confirmation/utils.test.ts

Result: passed.