make sure to not drop writes on close

Before, on close, we:

1. Weren't completing the write.
2. Flushing the buffer without waiting the latency delay.

This fixes that by using two separate channels for close/reset and ignoring the
close channel in deliverOrWait.

update go-stream-muxer

* Fix the tests to work with separate reset/close methods.
* Ensure we interrupt writes on reset.
* Always delay the proper time even if we're sending short messages.
* Copy buffers as we send them. `Write` is not allowed to hang onto buffers. If
  we run into performance issues, we can always add a buffer pool.

Protocol Multiplexing Example: Fixing build instruction so copy and pasting from the Readme works

As is go build ./examples/protocol-multiplexing-with-multicodecs
will make the binary name protocol-multiplexing-with-multicodecs
so the next command ./multicodecs won't run
using -o will name the outputfile

gx: update go-ws-transport

Fix the go get command.

We need to download dependencies for all packages in the repo, not just the
root (there are no packages at the root).

fixes #219

examples/echo: recommend -secio

When not using -secio, this command prints a warning. This confuses users so we
should just tell users to use it in the instructions.

fixes #179

gx: update go-cid, go-multibase, base32

gx: update go-reuseport

Summer cleaning

docs: refresh the readme, add more information for new contributors, add new logo, make it match js-libp2p

gx: update go-testutil