Enable Fully Offline Functionality

[bonedaddy]

Currently TemporalX works offline, and if not connected to any other peers, but it will encounter some issues when invoking functionality that expects to have peers. Given our use cases, this isn't really a problem, as it is unlikely TemporalX will ever be used in these situations.

It is generally assumed that when you're running TemporalX you will be connected in a replication cluster, which ensures persistent connectivity between all peers. Additionally it is also assumed that you will be operating either in the public IPFS network, or a private IPFS network with more than 1 peer.

That being said, it could come up that users want to use TemporalX in a fully offline scenario. For this it will be useful that we integrate with some of the offline routers, and dagservices that are supported by libp2p