[SHOT-187](feat: SH) - Add support for migrationTimeoutSeconds

[mimartin12]

🎟️ Tracking

https://bitwarden.atlassian.net/browse/SHOT-187
https://bitwarden.atlassian.net/browse/PM-37891

📔 Objective

Adds an input for migrationTimeoutSeconds, which is advanced configuration for users who may have large databases and require more time to run database migrations.

See bitwarden/server#8143

[github-actions]

🤖 Bitwarden Claude Code Review

Overall Assessment: APPROVE

Reviewed the new jobs.db.migrationTimeoutSeconds option, which is plumbed through as a -t argument on both the pre-install and post-install MSSQL migrator jobs and as a globalSettings__sqlServer__migrationExecutionTimeoutSeconds entry in the pre-install hook ConfigMap. The option is opt-in and defaults to empty, so rendered output is unchanged for existing installs; the post-install if/else if branching preserves the prior transition-args behavior for both fresh installs and upgrades. The regenerated values.schema.json matches the new values.yaml entry, and new unit tests cover the ConfigMap key and all three post-install arg permutations.

Code Review Details

• ♻️ : New args logic in the pre-install migrator job has no helm-unittest coverage, unlike the equivalent post-install change
  • charts/self-host/templates/pre-install-db-migrator-job.yaml:97-99
• 🎨 : Document the unlimited-timeout value as quoted "0"; an unquoted 0 fails values.schema.json type validation
  • charts/self-host/values.yaml:891-894

Both findings already have open inline threads from the previous review pass; no new inline comments were added.

PR Metadata Assessment

• ❓ : The version:patch label is applied, but CONTRIBUTING.md maps "new configuration options" to version:minor.