feat(helm): add auto-environment values to k8s-reporter chart

[mbevc1]

• Expose the CLI's --auto-environment flag and its companion flags
  (--environment-description, --include-scaling, --exclude-scaling)
  as reporterConfig.* values on the k8s-reporter chart, so the reporter
  CronJob can auto-create Kosli environments (type K8S) on first run
  without editing the chart.
• Chart version bumped to 2.6.0 and the values table in README regenerated. Also bumped CLI to 2.33.3
• Remove obsolete conditionals empty spaces (will render smaller output and triggers changes)
• Follow-up feat: add --auto-environment flag to kosli snapshot #1028

[claude]

Claude finished @mbevc1's task in 1m 20s —— View job

---

PR Review — Helm auto-environment values

• Gather context (diff vs origin/main, prior review comments)
• Verify prior review feedback was addressed
• Review the chart template changes
• Post review summary

This PR only touches the k8s-reporter Helm chart (no Go code), so the go build / go vet / go mod tidy gate is not applicable here.

✅ Prior review feedback — all addressed

Prior comment	Status
Quote the description value (: → invalid args)	✅ cronjob.yaml:117 now uses {{ ... | quote }}
includeScaling string-truthiness footgun (--set-string ...=false)	✅ cronjob.yaml:119 now guards with kindIs "bool" for a real tri-state
Release sequencing / v2.34.0 not yet published	⚠️ still worth confirming — see below

Correctness check

• Verified the flags the chart emits actually exist and are inherited by snapshot k8s: addAutoEnvironmentFlags registers --auto-environment, --environment-description, --include-scaling, --exclude-scaling as persistent flags on the snapshot group (cmd/kosli/snapshotAutoEnvironment.go:37-40). ✅
• The tri-state logic emits at most one of --include-scaling / --exclude-scaling, so it never trips the CLI's mutual-exclusion guard (only one of --include-scaling, --exclude-scaling is allowed, snapshotAutoEnvironment.go:63). ✅
• null default for includeScaling correctly falls through kindIs "bool" → no flag emitted → server default. ✅
• The whitespace cleanup ({{- chomping) is a nice tidy-up and renders a tighter args: block.
• values.yaml, README.md, and template are consistent; docstrings clearly note the "shared by all environments / existing environments never modified" caveats. 👍

⚠️ One thing to confirm before merge/publish (release sequencing)

Chart.yaml pins appVersion: "v2.34.0", and the image tag defaults to .Chart.AppVersion (cronjob.yaml:60). The latest published CLI tag is v2.33.3 — v2.34.0 is not tagged yet. The auto-environment feature is on main (confirmed above), so v2.34.0 is the right pin provided that's the release carrying it.

Action: don't publish chart 2.6.0 until CLI v2.34.0 is actually released, otherwise a default helm install will ImagePullBackOff on a non-existent image tag. Also note the PR description still says "bumped CLI to 2.33.3" while the chart pins v2.34.0 — worth reconciling the description so reviewers aren't confused.

Nit (optional)

• environmentDescription is a single shared value across all auto-created environments — this is documented, so it's fine as a deliberate limitation. If per-environment descriptions are ever needed, that'd be a follow-up.

Summary

Clean, well-documented follow-up to #1028. All earlier review feedback is incorporated and the emitted CLI flags are valid. The only remaining item is the release-ordering of the chart vs. CLI v2.34.0 — a process check, not a code issue. Looks good to me. ✅