feat: Upgrade WsStore, introduce promise-wrapped connect/authenticate for WebSockets, fix futures WS event routing

[tiagosiebler]

Summary

• Bump audit dependencies
• Upgrade internal WsStore utility class to latest.
• Promise-wrapped connect & authentication workflows for WebSocket client (resolves There is no way to force connection in the start of ws as we can do in bybit or binance #84)
• Upgraded under the hood BaseWSClient architecture to follow midflight-request model, in line with our other SDKs.
• Handle futures pong events (resolves isWsPong not working correctly for Futures #85)
• Fixed unhandled futures market data event pipeline (resolves isWsPong not working correctly for Futures #85 market data warning)
• Upgraded Web Crypto API integration to support Ed25519 & RSA mechanics
• Wrap event emitter in try catch for clearer context when exception originates outside SDK.

Additional Information

PR Checklist

As part of the PR, make sure you have:

• No breaking changes / documented all breaking changes clearly.
• Updated & checked that all tests pass.
• Increased the version number in the package.json
• Checked npm install runs without issue.
• Included the package-lock.json, if it changed after npm install
• Checked npm run build runs without issue.
• Updated the endpoint map (optional, if you know how).
• Run llms.txt generator (optional, if you know how).
• Check open issues
• Validate WS auth/connect/resub mechanics work as before
• Validate heartbeats work as expected
• Validate public topics, spot
• and futures
• Validate auth
• validate private topics
• validate resubscribe on reconnect