NetConn has to close the connection to interrupt in progress reads
and writes. However, it can block reads and writes that occur
after the deadline instead of closing the connection.

Closes #228

See https://github.com/nhooyr/websocket/issues/182

Closes #182

- For JS we ensure we indicate which size initiated the close first from our POV
- For normal Go, concurrent closes block until the first one succeeds instead of returning early

I changed my mind after #103 as browsers include a wasClean event to indicate
whether the connection was closed cleanly. From my tests, if a server using
this library prior to this commit initiates the close handshake, wasClean
will be false for the browser as the connection was closed before it could
respond with a close frame. Thus, I believe it's necessary to fully implement
the close handshake.

@stephenyama You'll enjoy this.

math/rand was being used inappropiately and did not have
a init function for every file it was used in.

Closes #150

- Also allows SetReadLimit to be called concurrently which is a nice
  touch

Closes #153

Realized I can at least make the Reader/Writer/SetReadLimit methods
work as expected even if they're not perfect.

Updates #88

Closes #121

The boys in the office hated it.

Highly unfortunate but makes sense as it seems confusing.

Will be cleaner in GitHub as the README.md is the first
thing you will see instead of a massive directory listing.

Closes #134

Closes #125

Minor API change, will need to document clearly in release notes.

Also simplified and refactored the Conn tests.

More changes soon.

Closes #113

Closes #111
Closes #112

See https://github.com/nhooyr/websocket/issues/100#issuecomment-508148024

Closes #101

Closes #100