chore: Add the optional "Client-Version" header in the Bridge Controller

[dan437]

Explanation

Adds the optional "Client-Version" header into API calls from the Bridge Controller. E.g. "Client-Version": "13.5.0"

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

Adds an optional Client-Version header to bridge and price API requests, plumbed from BridgeController to fetch utilities, and updates exports, tests, and changelog.

• Bridge Controller:
  • Accepts optional clientVersion in BridgeController constructor and stores it.
  • Passes clientVersion to fetchBridgeQuotes and fetchAssetPrices.
• Fetch Utilities:
  • Replace getClientIdHeader with getClientHeaders(clientId, clientVersion) to include optional Client-Version.
  • Update fetchBridgeTokens, fetchBridgeQuotes, and price fetching to use getClientHeaders and accept clientVersion.
  • Export getClientHeaders from src/index.ts.
• Tests:
  • Update unit tests to pass clientVersion and assert Client-Version header in requests and call signatures.
  • Snapshot expectations updated accordingly.
• Changelog:
  • Note addition of optional Client-Version header to bridge API requests.

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

[dan437]

the “X-” prefix for custom HTTP headers (like X-Client-Id) was deprecated by IETF in RFC 6648 (2012). RFC 6648 states new parameters SHOULD NOT use the “X-” prefix, that's why I just simply call it "Client-Version" here.