Data management tools for playing BattleTech

chore(repo): adopt the sibling repos' hooks, and two of our own master

Takes prek.toml's shape from infra, headquarters and arena, keeping what this repo has files for and dropping what it does not: no terraform, no prettier or astro, no ruff. check-xml earns its place on one file, bridge/log4j2-quiet.xml, which nothing else parses until MegaMek refuses to start. Two hooks are this repo's own. crate-boundaries runs the boundary check when a Cargo.toml changes, which is the file a boundary breaks in - a `use` cannot add a dependency, and the breakage otherwise surfaces much later as "why can this not compile to wasm". commit-scope checks Conventional Commits and that the scope names an epic in headquarters' plan/. That scope check differs from headquarters' in two ways on purpose. It enforces the form as well as the scope, since this repo has had the convention since its second commit. And the epic ids are written down rather than read from plan/, because helm has no plan/ and a sibling checkout is not guaranteed to exist - a list that is occasionally stale beats a hook that passes silently whenever a directory is missing. cargo clippy runs with -j 2, which the siblings do not need. A full-parallel cargo build has taken this machine down, and a hook runs on every commit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>