Datastore Synchronicity Audit

This issue is a placeholder to keep track of which libp2p and IPFS components use Datastores and what level of synchronicity are required from the components.

This is in preparation for implementing #137 and switching the IPFS Badger implementation to have synchronous writes turned **off** by default.

If you know of any places where the datastore is used and where synchronicity may be required please either add in a comment or just modify this post below this line:

----------

Adding Files to IPFS: Needs to synchronize after a single Add operation is complete
Removing Files from IPFS: No synchronization required (could be picked up in GC)
Pinning (Add + Remove) from IPFS: Required after each operation
IPNS Updates: Needs to sync after Put
DHT Record Updates: No?
Record Routing Updates: No?
Peerstore: No
Recording Metrics: Probably not

Filestore: ?
Badger: Just enable Sync if async flags is enabled
FlatFS: No
S3: No