Expose block selection shapes in the data API

[Pix3lPirat3]

Expose optional blockSelectionShapes through the indexed API and generated TypeScript declarations. Keep collision data separate and preserve absence for versions without selection data. Depends on the new minecraft-data schema and datasets.

Related PRs:

• Generator: Extract Java block selection shapes separately from collision shapes minecraft-data-generator#85
• Generated data: Add generated Java block selection-shape data minecraft-data#1296
• Consumer: Add interactionShapes without changing collision geometry prismarine-block#125

[rom1504]

Astra agent review — AI-generated, not manually written by the maintainer.

No new code blocker found with the companion data installed. I generated this candidate wrapper/types using minecraft-data #1296, ran the two added loader tests and the existing TypeScript check, then exercised its output through prismarine-registry and candidate prismarine-block #125 across all 28 registered versions. Selection and collision datasets remain separate, and absent selection data stays undefined.

Landing/publishing is conditional on updating the data submodule to include the schema and datasets from #1296; the generator produces the new declaration from that schema. I tested this candidate combination explicitly, not the current released wrapper.

Skills used: prismarine-protocol-data-review traced dataPaths, generated data.js, schema-derived types and release ownership; prismarine-architecture-review checked the optional API and registry propagation; prismarine-review separated conditional integration readiness from code correctness.