Adds WebSocket server support

[dkoontz]

Adds WebSocket server capabilities.

This is mostly modeled after the HttpServer module. There are tests but I haven't integrated it into a real application yet (going to work on gren-lang/browser#101 next so I have both parts to test with).

[dkoontz]

I pushed a new commit addressing your comments. I also noticed that I forgot to update the integration script runner and that all the integration tests were on 0.6.2 so I updated those to 0.6.3.

[robinheghan]

Hey @dkoontz , excellent stuff!

After my last review I thought of a few other things, and didn't add those comments to this issue. In any case, here they are:

1. Did you look into using Stream for the implementation? We recently updated HttpClient to use Stream as the underlying primitive, so that's something to look at. We kinda want to use Stream wherever we can to unlock whatever synergy effects there are.

2. Since you mention doing a WebSocket client next: do you think it would be possible to implement a Node.js compatible WebSocket client? I see v20 of Node.js and onwards have a experimental implementation of the browser API. If possible, the client could be implemented in gren-lang/core, where we eventually plan to move the node based HttpClient as well

[robinheghan]

We're getting close!

I have a few notes on the API.

Whenever we get a new connection, we give the user this record:

{ connection : Connection
, readable : Readable Message
, textWritable : Writable String
, binaryWritable : Writable Bytes
}

I think Connection should suffice here. The WebSocketServer.Connection module can expose functions that takes in a Connection and returns the readable and or writable stream.

I also think that instead of having two writeable streams, one for string and one for bytes, should be reduced to a single Writeable Message instead.

I also wonder why there are send and sendBytes functions in WebSocketServer.Connection. Shouldn't this be handled by the writable stream? 🤔

Also, should Connection, connectionId and Message be moved to the WebSocketServer.Connection module?

In summary:

• Remove send and sendBytes from WebSocketServer.Connection (unless there's a good reason for keeping them?). Communication over the web socket should be handled by streams.
• Add readStream : Connection -> Stream.Readable Message and writeStream : Connection -> Stream.Writable Message to WebSocketServer.Connection.
• Simplify WebSocketServer.onConnection to only return a Connection.
• Move Connection, connectionId (rename to id?) and Message to `WebSocketServer.Connection.