[AlinsRan]

The built-in wait-etcd init container cannot currently be given resource requests/limits or a container security context. This prevents users from configuring it for resource quotas and non-root execution policies.

Add independent initContainer.resources and initContainer.securityContext values for both Deployment and DaemonSet workloads. Both default to {} and are omitted when empty, preserving existing behavior and applicable pod-level security settings. Include configuration examples, non-root UID guidance, and regenerated documentation. The chart version is unchanged.

This is an alternative to #796 with values defaults, documentation, and empty-value handling included.

Fixes #784
Fixes #771

Validation:

• helm lint charts/apisix passed.
• Eight Helm rendering scenarios passed: Deployment/DaemonSet with defaults, custom settings, null settings, and etcd disabled. Assertions also checked pod security context, APISIX container isolation, and preservation of extra init containers.
• Regenerated README with helm-docs; git diff --check passed.
• No live cluster installation was performed.