Drop obsolete SaltStack Python carve-out from policy + antipattern CI

[hyperpolymath]

Context

SaltStack has been retired (infrastructure now uses Terraform + Ansible). The language policy and CI still encode a SaltStack-specific Python exemption that is now meaningless and misleading.

Stale references to remove/correct

• .github/workflows/rsr-antipattern.yml:
  • "Check for Python (non-SaltStack)" step filters salt / _states / _modules / pillar — these exemptions no longer apply; Python is now banned with no exemption. Step should fail on any non-allowlisted .py.
  • Summary banner text: "Allowed: ... SaltStack (Python)" and "Blocked: ... Python (non-Salt)" — update to reflect Python fully banned.
• .claude/CLAUDE.md and scaffoldia/.claude/CLAUDE.md: the banned table says Python | Julia/Rust/ReScript; add an explicit note that the former SaltStack exemption is withdrawn (infra = Terraform/Ansible, which need no first-party Python).
• Any other .claude/CLAUDE.md files in the repo with the same table.

Notes / ordering

• This depends on the git-cola Python file being removed first (companion issue), otherwise tightening the check just keeps CI red.
• Terraform (HCL) and Ansible (YAML) introduce no first-party Python, so no new exemption is needed.

Acceptance criteria

• antipattern-check Python step has no SaltStack-specific logic
• Policy docs no longer reference a SaltStack Python exemption
• CI green once the git-cola file is gone