Hotfix pubsub subscribe

[v-stickykeys]

Motivation

Our ipfs node on infra is going down periodically (reason tbd) and when it reboots we stop receiving pubsub messages.
Created an issue on js-ipfs repo here ipfs/js-ipfs#3465 -- the error handler for pubsub is broken in Node.js

Changes

• Check if we are subscribed every 60 seconds and resubscribe if we are not
• Also updated infra https://github.com/3box/ceramic-infra/commit/164ba63a21b82d5aba6da27dee457079930eb292 to not subscribe from the IPFS API node itself because it was causing this issue Client is not subscribed to topic but API node is ipfs/js-ipfs#3467
• Small change to check that document context includes anchorService before removing listeners (which was breaking tests)

[v-stickykeys]

This is actually breaking a lot of tests..
I think (1) because pubsub.ls is not mocked and (2) because it creates a new Node.js Timer with setInterval and requires dispatcher.close to be called to clean it up.

Because this is a hotfix anyway I'll see if I can modify some of the code to avoid a lot of test refactoring for now

[oed]

Few comments.

[stbrody]

A few small nitpicks, but my main question is if we can avoid the logic that checks if we are subscribed and just always try to subscribe unconditionally.

[v-stickykeys]

@stbrody yeah as joel mentioned it throws an error that you are already subscribed. But agree it's probably worth just doing that in case the ls returns unexpected results (which it has in certain conditions like if the node has already attempted to subscribe before the client has).

[oed]

Looks good, just one Q

[stbrody]

Nice! This looks much cleaner. LGTM mod one comment about making sure the console doesn't fill with errors when everything is actually working as expected