chore(auto-upgrade): run cronjob hourly at :23 (prod cherry-pick)

[saadqbal]

Summary

• Cherry-pick of the same commit on #112 (dev-side), branched off main so this PR contains only the schedule change — no other unshipped develop commits ride along.
• Switches default autoUpgrade.schedule from "23 2 * * *" (daily 02:23 UTC) to "23 * * * *" (hourly at :23) so deployed clients converge on the latest chart within ~1h instead of ~24h.

Refs #111. Merge alongside #112; either order is fine since both PRs carry the same single-file change.

Test plan

• Confirm diff vs main is exactly the 2-line schedule: change in client/values.yaml
• helm template ... | grep -A1 schedule: renders 23 * * * *
• client/tests/auto_upgrade_test.yaml passes (helm unittest client/)
• Post-deploy: kubectl get cronjob -n <ns> -l app.kubernetes.io/component=auto-upgrade shows hourly schedule

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes the default self-upgrade CronJob cadence from daily to hourly, increasing how often clusters run a helm upgrade with cluster-admin privileges and how quickly any bad chart release could roll out.

Overview
Updates the default autoUpgrade.schedule from daily "23 2 * * *" to hourly "23 * * * *", so deployed clients check for and apply chart upgrades within ~1 hour instead of ~24 hours.

Adjusts the Helm unittest (client/tests/auto_upgrade_test.yaml) to assert the new rendered CronJob schedule.

^{Reviewed by Cursor Bugbot for commit cafaf27. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 4fc3d16. Configure here.}