[HealthController] Perform rolling update of scheduler versions

[hspedro]

• refactor(healthcontroller): perform rolling update

It is now responsibility of the healthcontroller to perform a rolling update. When there was a switch on the current scheduler active version we need to rollout pods with the new version. Health controller either does autoscaling or rolling update.

On rolling update, the following will happen:
1. Are there rooms with a previous scheduler version? If so, start
update
2. Compute how many rooms we can surge (above desired from autoscaling)
3. Enqueue priority operation to create this rooms
4. Check how many Ready rooms we have above desired from autoscaling
5. Enqueue operation to delete those rooms - they are a buffer, should
never offend readyTarget

• refactor(switchversion): do not replace pods

  The switch version operation will just update the scheduler version.
  Let healthcontroller perform the rolling update

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.

Project coverage is 64.27%. Comparing base (bb118c8) to head (a71052f).
Report is 5 commits behind head on main.

Files	Patch %	Lines
internal/adapters/runtime/kubernetes/scheduler.go	0.00%	3 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #618      +/-   ##
==========================================
- Coverage   64.30%   64.27%   -0.03%     
==========================================
  Files          39       39              
  Lines        2905     2911       +6     
==========================================
+ Hits         1868     1871       +3     
- Misses        909      913       +4     
+ Partials      128      127       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.