feat: Websocket connection uptake

[purnimavenkatasubbu]

- What I did
Implemented WebSocket support for inbound connections in the secondary server. Added InboundWebSocketConnection to handle WebSocket-based client connections.

- How I did it

• Created the InboundWebSocketConnection class, implementing the InboundConnection interface to handle WebSocket operations like writing, closing, and managing metadata.
• Updated AtConnectionFactory to support creating WebSocket connections via createWebSocketConnection.
• Modified InboundConnectionManager to manage WebSocket connections, ensuring proper pooling and handling of capacity limits.
• Added webSocketListener in AtSecondaryImpl to accept and handle WebSocket requests.
• Modified end-to-end test utilities and made the end2end12 job use websocket connections

- How to verify it
All tests pass

[gkc]

@purnimavenkatasubbu @VJag I've pushed some changes with some TODOs for you to get all of these changes covered by end to end tests. Once that's all done you could consider doing the same type of thing for the functional tests and running functional tests four times (dart stable socket, dart stable websocket, dart latest socket, dart latest websocket) instead of the current two (dart stable, dart latest)