Helm: worker strategy maxUnavailable value is ignored by template

Summary

openstudio-server/templates/worker/worker-deploy.yaml hardcodes maxUnavailable: 1 even though values.yaml exposes worker.strategy.maxUnavailable and docs/comments describe tuning it.

Current behavior

• Template line uses a literal: maxUnavailable: 1
• worker.strategy.maxUnavailable from values is not wired into the rendered Deployment

Expected behavior

• maxUnavailable should be sourced from values, similar to maxSurge
• If unset, use a safe default (current behavior can remain the default)

Why this matters

Operators cannot apply intended rollout controls from values files, which can cause unexpected rollout speed/disruption in large worker fleets.

Suggested fix

In templates/worker/worker-deploy.yaml, replace hardcoded maxUnavailable: 1 with value lookup from worker.strategy.maxUnavailable and fallback default.

Acceptance criteria

1. helm template reflects worker.strategy.maxUnavailable when set in values.
2. Existing default behavior remains when not set.
3. scripts/install-dry-run.sh checks pass.

Start with templates/worker/worker-deploy.yaml and compare its maxUnavailable handling with maxSurge and the worker.strategy settings in values.yaml. Run helm template with worker.strategy.maxUnavailable set and unset, then run scripts/install-dry-run.sh. Done means the configured value renders when set and the existing default remains otherwise.