BCI-2450: Health check for MultiNode to ensure that node is not in syncing state

[dhaidashenko]

This came up as a follow-up of testing on canary, by QA teams.

If an RPC node is newly setup, and still syncing the blockchain, it may not be ready for taking client requests. Currently, our MultiNode client marks this node as OutOfSync, and logs error statements in our logs, which is confusing for some NOPS.

Changes:

• Added separate node state syncing to differentiate it from outOfSyncStatte.
• Fixed reconnection bug for nodes with invalidChainID. We close ws connection, when transitioning node to this state, but do not reconnect.

[github-actions[bot]]

I see that you haven't updated any README files. Would it make sense to do so?

[cl-sonarqube-production[bot]]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
82.8% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube