test(bitswap) run synchronously to aid the scheduler

fix(bitswap) Put synchronously. Then notify async

to avoid letting client rely on order for correctness

misc:
* test network client getting more than max
* test for find providers
* rename factory method
* local network
* misc test improvements
* test bitswap get block timeout
* test provider exists but cannot connect to peer
* test sending a message async over local network

style(exch:bitswap) rename NetMessage adapter impl

yay deleting code.

@jbenet oh hai there!

> Why expose num bytes sent and received?

    Makes it easy to test consistency of the ledgers

> Got a better reason?

    Makes it possible to expose metrics to the people-facing API