Synchronize artifact build backend catalog

[shiny-code-bot]

Summary

• update the devkit-owned support catalog and lock from Hatchling 1.27.0 to 1.31.0
• make platform dependencies check compare staged addon build backends with the materialized devkit support catalog before publish
• retain the exact committed-byte publish-time validation as the final fail-closed gate

Evidence

CM, CM Website, and OPW artifact canaries all passed Launchplane authorization, then failed before Buildx with the same missing support requirement: hatchling==1.31.0. The tenant/shared addon metadata had advanced while docker/runtime-python remained at 1.27.0.

Validation

• 215 repository tests pass, 1 skipped
• Ruff check and format check pass
• package build succeeds
• CLI smoke succeeds
• focused Gemini-family review attempted; final independent code review found no blockers

Closes #87. Blocks are tracked from cbusillo/launchplane#1774 and cbusillo/launchplane#1768 until the real tenant canaries pass.