Feature request: Add per-peer control over uploading and downloading

This is a request to control whether a core is uploading or downloading on a per-peer basis.

Use case 1: User is on a metered internet connection (e.g. with bandwidth costs) and is connected to both local (same wifi network) and remote peers. User might want to only replicate in one direction (e.g. upload or download) with the remote peer.

Use case 2: User wants control over replicating data, but wants to know what data is available to replicate before deciding to download it. E.g. user wants to know the updated length of the core from a peer before deciding to download it.

Use case 3: With an authorization layer, a user might want to download data from a peer, but not allow uploads to that peer, e.g. for a peer that has authorization removed but still has important data that needs replicated.

It would be helpful to set a default for new peers, and add methods to control this for each peer, e.g.

const core = new Hypercore({ uploading: false, downloading: false })
core.on('peer-add', peer => {
  peer.setUploading(true)
  peer.setDownloading(true)
})

See https://github.com/holepunchto/hypercore/pull/499/files for a proof-of-concept naive implementation.

This issue supercedes https://github.com/holepunchto/hypercore/issues/305, which I think can be closed.

Review the proof-of-concept changes in pull request 499 and the related issue 305 first. Define the default and per-peer uploading and downloading controls described here, including the three use cases and the proposed peer methods. Done should provide independently controllable upload and download behavior for each peer and configurable defaults for new peers.