Add Code for Heartbeat Node

[Spaarsh]

Component

Heartbeat Node

Functionality Expected

1. To be spawned for every client instance automatically
2. Connect to the Server component independently of its respective Client component
3. Send Heartbeat requests to its Client component
4. Process Heartbeat responses
5. Send constant Heartbeat status to the Server component
6. Destruct upon inactivity from its client instance after a fixed amount of time OR upon signal from Server component

[HelixY2J]

Oke so currently both clients and the master server send periodic heartbeats to consul. Clients register themselves in Consul and then periodically update their status as well as master. So consul can deregister any node that stops sending heartbeats. The master queries Consul to get a list of active clients.If a client crashes or disconnects, Consul marks it as unhealthy and after a timeout (10s), consul removes it from the active service list. So when client stops sending heartbeats, consul removes it and the master will not discover it in the next query. Next, If we want clients to send heartbeats directly to the master instead of Consul, we would need to implement the heartbeat RPC defined in the proto file

rpc Heartbeat (HeartbeatRequest) returns (HeartbeatResponse);