DBC22-7174: Remove Liveness Probe from Tasks

[wmuldergov]

This is causing excessive resource usage and restarts.

📝 Submitter

🔗 JIRA Ticket

• Ticket Link: https://moti-imb.atlassian.net/browse/DBC22-7174

---

✅ Quality Assurance & Requirements

• Requirements Met: I have confirmed that all acceptance criteria from the JIRA ticket are fulfilled.
• Tested desktop in local or dev envs
• Tested mobile in local or dev envs
• Ran unit tests locally
• SonarCloud: I have verified that the SonarCloud analysis is clean/passing for this branch.

⚙️ Configuration & Environment

• New Env Variables: Does this PR require new environment variables? (Yes/No)

  If yes, please list them here and ensure they are added to secret manager, the .env.example. and the Vault by an STA.

🧪 How to Test (if required)

1. Deploy and confirm that the liveness probe for tasks is no longer in the deployment.

---

🔍 Reviewer Checklist

• Reviewed code for logic and cleanliness
• Re-tested desktop/mobile in local or dev envs
• Verified no new console warnings/errors
• Confirmed that any new env variables are understood/documented

[ray-oxd]

@wmuldergov pushed a replacement for the liveness probe script. Please review the changes in leader-election.py

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[wmuldergov]

@wmuldergov pushed a replacement for the liveness probe script. Please review the changes in leader-election.py

@ray-oxd I tested the change and noticed a few issues due to how timestamps are handled. It was off by 7 hours. I fixed that now and it works well in dev. Feel free to approve and merge to main.