feat: add security data type in bridge metrics

[GeorgeGkas]

Explanation

Add token_security_type_destination as security classification of the destination token (securityData.type). Omitted if securityData is not present.

References

Related: https://github.com/Consensys/segment-schema/pull/544
fixes: https://consensyssoftware.atlassian.net/browse/SWAPS-4420

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

Low Risk
Low risk: type-only analytics payload changes (new optional field) plus a changelog entry; no runtime logic changes.

Overview
Adds a new optional metrics property, token_security_type_destination, to multiple Unified Swap/Bridge analytics event context payload types (including InputSourceDestinationSwitched, Completed, and Failed) so clients can report the destination token’s securityData.type when available.

Updates the bridge-controller changelog to document the new analytics field.

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

[infiniteflower]

As discussed we will close this in favor of this PR. Please reopen if needed.