feat(kasm): separate db-init-job annotations (upstream PR #29)

[darkhonor]

Summary

• Ports kasmtech/kasm-helm#29 by @matonb
• Creates dedicated components.init_db.annotations and components.init_db.labels config
• db-init-job template uses init_db instead of api variables
• Default includes helm.sh/hook: pre-install; GitOps users can override to prevent deadlocks

Why

Enables adding pre-upgrade and hook-delete-policy via values overrides instead of template forks. Complements our issue kasmtech/kasm-helm#35 findings 3 and 4.

Test plan

• helm lint charts/kasm
• helm template with default values — verify db-init-job has helm.sh/hook: pre-install
• helm template with custom components.init_db.annotations — verify override works

🤖 Generated with Claude Code

[darkhonor]

Closing: superseded by upstream kasmtech/kasm-helm 1.1190.7 (Kasm 1.19.0), which addresses this natively. We're retiring the forked charts/kasm chart from this repo and deploying the upstream chart (https://helm.kasm.com) directly via Fleet.

• feat(kasm): separate db-init-job annotations (upstream PR #29) #57: upstream db-init is no longer a Helm hook; extraAnnotations.job covers custom annotations.
• fix(kasm): add db initialization check before migrations (upstream PR #30) #58: upstream db-init verifies zones + Alembic (head) before running startup.sh, so re-runs exit early.
• feat(kasm): add extraVolumes, extraEnv, and initContainers (upstream PR #32) #59: upstream supports extraVolumes, extraVolumeMounts, extraContainers, and extraInitContainers globally and per component.