Fix initContainers resource rendering when not defined in values

[Copilot]

The initContainer template files attempted to render initContainers.resources without checking if the parent initContainers object exists, causing template evaluation failures when users omit these optional configurations.

Changes

• Template safety checks: Added conditional guards in _initContainers-wait-for-infrastructure-dependencies.tpl and _initContainers-wait-for-other-components.tpl to verify both initContainers and initContainers.resources exist before rendering
• Chart version: Bumped to 0.8.4

Technical detail

# Before: Would fail if initContainers undefined
resources:
  {{- toYaml (get $ctx.Values $component).initContainers.resources | nindent 4 }}

# After: Safely handles missing configuration
{{- if and (get $ctx.Values $component).initContainers (get $ctx.Values $component).initContainers.resources }}
resources:
  {{- toYaml (get $ctx.Values $component).initContainers.resources | nindent 4 }}
{{- end }}

This allows deployments to proceed without explicitly defining initContainers.resources for each component (api, ui, evalServer, daServer).

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.