feat: first class support for websockets

[BlankParticle]

fixes #307

There was some discussion around how we should do this, but it died down
I landed on a design that doesn't add any extra runtime dependency, the user needs to provide the websocket server themselves, which is a good compromise.

I am opening this PR so we can do discussion around this and easily reason about this,
this is not the final design and I will update this PR accordingly to the reviews/comments to better fit the goal

code was ported and adapted from @hono/node-ws

[yusukebe]

Hey @BlankParticle

Sorry for being late. I think the direction of this PR is good! So, can you finalize this, or is this ready for review?

I'd like to include this change to the next major version v2: #316

[BlankParticle]

This version is ready for review where you need to provide your own websocket server.
I was wondering if you have considered having ws as peer dependency as @nakasyou said would be fine in #307
else this PR is good to go

[yusukebe]

@BlankParticle

Simple question. If you add ws as peerDependencies, the user should install ws even though they don't use WebSocket? If so, adding ws to peerDependencies is not necessary; only adding docs is better, I think.

[BlankParticle]

this design works then, users will need to pass in their own server,
this is also better for use cases like if you have a ws compatible library or you want to pass in an existing server like in a vite plugin

this PR is ready to go

[yusukebe]

@BlankParticle Okay!

Hey @nakasyou can you review this? (We don't need to add ws to peerDependencies).

[nakasyou]

It looks great!