incorrect offset should provide clearer indications

[RaekwonIII]

By now it has become clear that this message:

2024-08-30T08:28:56.951050Z    DEBUG    logger is ready    {"level": "debug", "encoder": "json", "format": "capitalColor", "file_options": null}
2024-08-30T08:28:56.954317Z    INFO    dkg-initiator    🪛 Initiator`s    {"Version": "v2.1.0"}
2024-08-30T08:28:58.047233Z    DEBUG    dkg-initiator    operator responded    {"IP": "https://lido-ssv.sre.ideasoft.io/", "method": "health_check", "status": 400}
2024-08-30T08:28:58.048343Z    ERROR    dkg-initiator    😥 Operator not healthy:     {"error": "incorrect offset", "IP": "https://lido-ssv.sre.ideasoft.io:443"}

generally indicates that the node is running a different version from the one performing the ping (or ceremony). But the error message should be clearer.

Instead of incorrect offset, it could say incorrect offset: likely due to version mismatch, or, even better incorrect offset: expected version v2.1.0, found <node version...

People keep opening tickets and asking questions about this, even if we add it to the Troubleshooting page, not everyone takes time to read it...

[pavelkrolevets]

Fixed at PR

• for ping unfortunately we cant unfortunately get a version from messages coming from operator from old versions v0.0.1, v1.0.1
• added messages probably of old version, please upgrade