Helm: web init waitForDb settings defined in values are not used

Summary

values.yaml and values.schema.json define web.initContainer knobs (image, waitForDb.maxAttempts, waitForDb.retryDelaySeconds), but templates/web/web-deploy.yaml currently hardcodes the init container behavior.

Current behavior

• Init container image is hardcoded to alpine
• DB wait loop is hardcoded to seq 1 300 and sleep 3
• value knobs are ignored at render time

Expected behavior

• Template should read:
  • web.initContainer.image (with sane default)
  • web.initContainer.waitForDb.maxAttempts
  • web.initContainer.waitForDb.retryDelaySeconds

Why this matters

This is a configuration drift/footgun: operators may tune these values in overlays and assume they are active, but runtime behavior remains fixed.

Suggested fix

Wire the web init container command/image to the existing values fields and preserve current defaults (300 attempts, 3s delay) when unset.

Acceptance criteria

1. helm template output changes when those values are overridden.
2. Defaults match current behavior if not overridden.
3. scripts/install-dry-run.sh checks pass.

Start with values.yaml, values.schema.json, and templates/web/web-deploy.yaml to trace the existing web init container settings and command. Render the chart with helm template using default and overridden values, then run scripts/install-dry-run.sh. Done means overrides affect the image, maximum attempts, and retry delay while defaults remain 300 attempts and 3 seconds.