Status update logic change

[Filter94]

Description

Currently if status update is missed or it returns invalid fork id, the nodes disconnect. I think pass on a few failed status updates is a better strategy that is not detrimental to the overall network, so maybe instead of the disconnection we can do a penalization

Motivation

I think it will improve the network connectivity in case of a fork id change (Chain upgrades) and sporadic network issues

Tasks

• Replace the disconnection mechanism with penalization mechanism on status update failure

Acceptance criteria

• Nodes stay connected to each other in case of a single missed status update and/or failed fork id check

Risks

• It may leave some unavailable nodes in the list of connected peers which may impact the syncing and block propagation logic

Remember to

• Add the documentation label in case there is an impact on the documentation
• Add priority and team labels
• Add Task for updating the Runbook or adding/updating existing metrics and alerts.