style(helm): split helm template | kubeconform pipeline for readability

[rguichard]

Addresses an Aikido finding on PR #90 (validate-helm-charts.sh:121).

Split the single-line helm template . | kubeconform ... > file 2>&1 across continuation lines with a comment. The if ! guard is intentionally kept: under set -o pipefail it detects a failure in either stage, whereas Aikido's suggested bare-command + $? form would abort the function under set -e before the status could be captured. No behaviour change.

🤖 Generated with Claude Code

[aikido-pr-checks]

The new comment says pipeline status reflects only kubeconform, but with set -o pipefail failures in helm template also fail the pipeline; this comment describes impossible behavior for this script.

Suggested change

	# resulting manifests with kubeconform. The pipeline's exit status
	# reflects kubeconform (the last command), which is what we check.
	# resulting manifests with kubeconform. With pipefail enabled, the
	# pipeline fails if either helm template or kubeconform fails.

Details

✨ AI Reasoning
​The updated explanatory comment asserts that the pipeline status comes from the final stage only. That assumption cannot hold in this script because pipeline failure behavior is globally altered to fail when any stage fails. This creates a clear contradiction between documented logic and actual execution behavior, which can mislead future changes and debugging.

_{Reply @AikidoSec feedback: [FEEDBACK] to get better review comments in the future.
Reply @AikidoSec ignore: [REASON] to ignore this issue.
More info}