ci(devsecops): enforce guardrail gates in blocking mode (#554)
Phase C enforcement for the DevSecOps Guardrails epic (jmservera/SquadScope-Coordinator#33), closes #545. Flips the Phase-A warning-only jobs to blocking now that the Phase B baseline (#543) is clean. - lint.yml: drop job/step continue-on-error; `ruff check .` is blocking and a new `ruff format --check .` step enforces formatter-owned line length. - checkov.yml: drop --soft-fail and continue-on-error; new IaC/Actions misconfigurations fail the build. Accepted findings use justified inline `# checkov:skip`. SARIF upload retained (if: always()). - security-scanning.yml: drop continue-on-error on zizmor-scan; default-persona findings now fail the build. - pytest already blocks via the `CI / Python` job (no change needed). Updated docs/devsecops/*-baseline.md Phase C status. Verified locally: ruff, checkov (no --soft-fail), zizmor (regular persona), and `pytest tests/` (1209 passed) are all green. Repo admins: mark these as required checks in branch protection — `Lint / Ruff`, `Checkov / Checkov IaC/container scan`, `Security Scanning / GitHub Actions Security Scan (zizmor)`, `CI / Python`. Depends on #543 and #544. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>