Release 1.33.0

[OptimNow]

Minor release-train bump (all four version holders together: plugin.json, marketplace.json metadata.version, mcp_server/pyproject.toml, server.json x2), plus the marketplace description topic list updated for the new domains.

Merge order: after #177. The payload is the content from #177 - six playbooks (the three commitment-mismatch ones that make the find_playbooks facet non-empty, and the three S3 lifecycle ones) and the new finops-kpis-benchmarking.md reference - so this PR must land second, or the tag ships without it. Content PRs merged since 1.32.1 (#172-#176: coverage heat maps, zombie-NAT window alignment, tool-surface rewrite) ride along.

Post-merge chain (automated): auto-tag v1.33.0 -> PyPI publish (gated by the pypi environment approval - Jean's manual control point) -> MCP Registry publish (waits for PyPI visibility).

Manual follow-up, in order:

1. Approve the pypi environment deployment in the Actions run.
2. Confirm the registry entry: https://registry.modelcontextprotocol.io/v0/servers?search=finops
3. Redeploy Alpic, then verify by calling the endpoint (initialize + tools/call list_references should report 34; find_playbooks(waste_category="commitment-mismatch") should return 3) - do not tick this from the source.
4. Re-run probes P11 and P12 through the connector (expected: gap -> GROUNDED) and log the cycle in pipeline/coverage-probes.md.