Extract src/websockets from Polykey to js-ws

[CMCDragonkai]

Specification

The websockets domain in Polykey can be extracted out in order to be re-used inside PKE.

Initial usage will just wrap around ws. So no runtimeless support yet. We would later extract the functionality of ws to have runtimeless support.

Proper runtimeless support would need to support TLS too. This is also where we can investigate how to unify the TLS between all the IO libraries. It's possible that the entire state machine can be done in pure JS without involving Rust/C++, it might be fast enough. Doing this would a be separate thing.

Additional context

• WebSocket Behaviour Alignment with Transport Layer #3
• Unifying the TLS libraries between WS, QUIC and Fetch/HTTPS Polykey#526
• Investigations into a Random Read and Random Write State Substrate for Keynodes Polykey#2

Tasks

1. Extract out src/websockets to js-ws
2. Implement the WebSocketStream muxing/demuxing on top of WebSocket connection
3. Ensure that library works in browser and also on nodejs.
4. Plan out the roadmap to support runtimeless operation (without ws)
5. Plan out the roadmap for unified TLS support - assuming runtimeless state machine is pure JS, then TLS operations would have to be exposed via JS routines too (this is necessary to support WSS)

[CMCDragonkai]

• Agent migration stage 2 Polykey#535 (comment)
• Agent migration stage 2 Polykey#535 (comment)

[CMCDragonkai]

The js-ws should have similar structure to https://github.com/MatrixAI/js-quic/tree/staging/src.

[CMCDragonkai]

There are pending changes in MatrixAI/Polykey#535 that affect WS. These should be extracted as well (or if it is merged by @tegefaulkes tomorrow).