feat: Add dynamic status check intervals with cooldown period and timeout handling

[StefanNemeth]

Problem

Static 120-second checks were inefficient for environments needing immediate feedback (e.g., post-deployment). However, when we set this down to like 10 seconds, we would fetch the latest status from environments that rarely change, even for the whole night.

Overview

This PR introduces dynamic status check intervals for environments:

• Frequent checks (10s) for environments with recent status changes or deployments.
• Less frequent checks (60s) for stable environments after a cooldown period (5 minutes).
• 10-second timeout for all checks to prevent long-running jobs.
• Trigger frequent checks when deploying to environment
• Update UI so it updates the "last check" regularly

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for 61170851	✅ 2.68%

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (6117085)	Report Missing	Report Missing	Report Missing
Head commit (3152be6)	4856	326	6.71%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#360)	112	3	2.68%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩

[thielpa]

Nice work!