feat(ci): migrate catalog from v1.1.1 to v2.2.0 + adopt PST renovate preset
Summary
Mechanical v1 -> v2 catalog migration for manifold (Go, 1.24).
- 4 component refs: `container`, `verify`, `binary`, `release` from `@v1.1.1` -> `@v2.2.0`.
- All kebab-case input keys -> snake_case per v2 contract.
- Drop `release.binary-names` (no v2 equivalent; release auto-links dist/*). Add `binary_job: binary-release` so the tag-time release links to the right binary job.
- Add `job_rules` to `binary` so the cross-compile runs on MR + default branch, not only tag pipelines. Closes the same coverage gap audit surfaced on assay.
`renovate.json`: extend the PST shared preset (`gitlab>gitlab-com/public-sector-tools/pipeline//presets/renovate.json`). Picks up Go module bumps, future catalog tags, golangci-lint via preserved local grouping rule.
Push rule fleet baseline already applied via API (was missing the optional `!?` for breaking-change markers).
Test plan
- MR pipeline green (lint, test, build, container path, dep-scan)
- Binary cross-compile now exercises on MR pipeline (was tag-only)
- Container build + cosign verify pass under v2.2.0