chore: align compliance status messages to NON-COMPLIANT

[mbevc1]

For ENV and snapshot assertions the CLI printed INCOMPLIANT, which did not match the NON-COMPLIANT framing used in the UI and elsewhere in the CLI. Align the wording in assert snapshot and get environment.

Closes #969

[claude]

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

---

Review: align compliance status to NON-COMPLIANT

• Gather context (diff + surrounding code)
• Static analysis (go build, go vet)
• Check for other INCOMPLIANT occurrences left behind
• Review code quality & consistency
• Post review summary

---

✅ LGTM. This is a clean, well-scoped wording fix that does exactly what it says.

Findings

• Completeness — A repo-wide search for INCOMPLIANT returns zero remaining matches, so the rename is exhaustive. Both user-facing sites are covered:
  • cmd/kosli/assertSnapshot.go:90 — the error returned by assert snapshot.
  • cmd/kosli/getEnvironment.go:86 — the state shown by get environment.
• Consistency — NON-COMPLIANT now matches the framing already used elsewhere in the CLI: getSnapshot.go:208, assertArtifact.go:194 (Error: NON-COMPLIANT), and getTrail.go:198 which explicitly handles "NON_COMPLIANT", "NON-COMPLIANT". Good alignment with the UI.
• Tests — The golden file in assertSnapshot_test.go:92 (Error: NON-COMPLIANT\n) and the test name were updated together, so the assertion actually covers the new wording rather than silently passing. 👍
• Static checks — go build ./... and go vet ./cmd/kosli/ both pass.

Minor observations (non-blocking, out of scope for this PR)

• assertArtifact.go:194 emits the failure via logger.Info("Error: NON-COMPLIANT") rather than return fmt.Errorf("NON-COMPLIANT") like assertSnapshot.go now does. The on-screen text matches, but the two commands signal failure through different mechanisms. Worth a glance to confirm the assert artifact exit code still behaves as intended — though that's pre-existing and unrelated to this change.
• The get environment path relies on env["state"].(bool) type assertions; no change needed here since this PR only touches the string literal, just noting the surrounding code assumes well-formed input.

Nice, tightly-scoped customer-facing fix — test and production code changed in lockstep.

[mbevc1]

Related docs change: kosli-dev/docs#290