Reconsider async send()

[sonnyp]

Currently, the send method is async and resolves when the message was sent or rejects if the message couldn't be sent.

Except when using WebSocket with the browser API because it doesn't expose a way to know the message was sent, they are simply queued.

Instead we could make send queue messages. It could also be used in conjunction with stream management.

Node.js and other JavaScript runtimes now implement globalThis.WebSocket and removing ws dependency would be nice to have as well.

Reconsider also sendMany

[sonnyp]

I just realized this is a thing now https://developer.mozilla.org/en-US/docs/Web/API/WebSocketStream

write returns a promise so we could adopt that and keep send as is.