Healthz check for deadlocks

[kmlebedev]

What problem are we solving?

When a deadlock occurs, the leader master server pretends to be alive
#4522

How are we solving the problem?

Define a deadlock in the liveness handles, which will allow the container to be restarted with the leader of the master and control will take another

How is the PR tested?

localy

make dev
curl -v -I  http://127.0.0.1:9333/cluster/healthz
*   Trying 127.0.0.1:9333...
* Connected to 127.0.0.1 (127.0.0.1) port 9333 (#0)
> HEAD /cluster/healthz HTTP/1.1
> Host: 127.0.0.1:9333
> User-Agent: curl/7.77.0
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Fri, 09 Jun 2023 11:24:46 GMT
Date: Fri, 09 Jun 2023 11:24:46 GMT

Checks

• I have added unit tests if possible.
• I will add related wiki document changes and link to this PR after merging.