The publish worker isn't currently used as the reduction of publish latency coming from moving to ceramic. But there are multiple places where the error recovery is basically non-existent, and we need a mechanism to continuously track and retry stuff like dpid minting, creating pubdatarefs, and other async tasks.

These should be idempotent for easy integrity checks, granular, and prevent all pods racing the queue.