Subscriptions should refresh when there are more able peers

[iduartgomez]

The scenario is such that when you subscribe initially, currently you are stuck with that peer. There is missing logic yet to recover subscriptions when the node you are subscribed to drops the network, but additionally to that, whenever you get new peer connections which are closer to the location of the contract they should substitute your current subscriptions in order to be more efficient on the number of messages sent around when relaying updates etc.

[github-actions]

Pivotal Tracker story: https://www.pivotaltracker.com/story/show/184207190

[kernelkind]

@iduartgomez Are you working on this issue? If not, I'd like to attempt it if that's ok

[iduartgomez]

You can go ahead, is in the backlog.

I can guide you through the chages needed if necessary too, and give a detailed reply. But will need to take a good look at the source and I won't be able next couple days.

Either way, is free to take.

[iduartgomez]

Actually... while I am working on fixes I am modifying some related things re. how we keep track of subscriptions, etc. so is probably better to wait for #907 to be merged @dowdyma1

[iduartgomez]

I think susbcriptions need some rethinking as there are some flaws on how we are doing them currently, any changes may affect this issue and both things may be improved at the same time in turn. So maybe is better to hold off a bit more for now re. this.

That said, this related task I think is more important to do and should be possible to fix without any blockers now:
When a connection is dropped, reestablish any subscriptions that relied on that connection