Daemon should support immediate reincarnation of cancelled subgraphs

[kriskowal]

What is the Problem Being Solved?

As discovered in #2217, peers race to connect and the loser of the race must invalidate the current incarnation of its CapTP reference to the remote gateway and its transitive dependents. This may lead to strange failure modes for “pinned” caplets. A pinned caplet would be a caplet that is expected to start up when the daemon restarts and remain running in the background across runs. It should also ideally be reincarnated immediately if it’s ever cancelled.

Either in the scope of supporting pins or as an additional effort, cancelling a connection that lost the crossed-hellos race should cause any pinned formulas to reincarnate immediately.