"stopped connection to gsb" is a very dangerous and silent killer

[etam]

It comes when no one expects him. After he hits his prey, it's running for a long time, seemingly fine, but not quite. It's believed that he's from the Heisenbug family.

He's name is "stopped connection to gsb"

A list of potential victims:

• stopped connection to gsb #752
• looping "Failed to unsubscribe Offer" so hard that "stopped connection to gsb"? #788
• [... WARN ya_net::central::service] Handlers disconnected #2222
• Yagna went into weird loop, spamming "Closing session" and DOSing web3 rpc #2388
• and it's suspected that there are many not reported, due to unclear circumstances of victims death.

I'd like to raise and highlight this issue, to handle it once and for all.

I think that is such case yagna should just die. It looks like some components are instead running, trying to communicate with other via gsb, but they get no responses and somehow continue to run.