feat: add health check in temporal service and retry with exponential backoff for Temporal client

[vikaxsh]

…ove health checks

Description

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Scenario A
• Scenario B

Screenshots or Recordings

Related PR's (If Any):

[vishalm0509]

Retry count is not equal to MaxRetryCount defined in the constant. Can you check once.

There is something in the library called backoff.WithMaxRetries, check if that can help

[vishalm0509]

In destination.go and source.go we are using

if c.tempClient != nil { 

}

Here we are checking

if c.tempClient == nil {
		utils.ErrorResponse(&c.Controller, http.StatusInternalServerError, "Temporal client is not initialized")
		return
	}

Can we make it consistent

[vikaxsh]

to avoid extra lines of code, at some places we not using response from function

[vishalm0509]

if c.tempClient == nil {  
        utils.ErrorResponse(&c.Controller, http.StatusInternalServerError, "Temporal client is not initialized")  
        return  
    }

I mean we are throwing this error only in job, and not in source and destination. Just to make it consistent.

[shubham19may]

Closing as already implemented backoff in refactoring.