schemas: add registry tags schema and audit

[VasilisDragon]

Problem

This PR was originally based on #1080's 1.21.8 four-registry output. The replacement generator work uses full resource locations and can emit any keyed registry, so the schema and repository checks need to cover the final representation.

Fix

• validate full registry, tag and member resource locations while preserving empty tags;
• reject duplicate members and unresolved #tag references;
• add a PC-only audit for canonical ordering, dataPaths targets, orphan files and mapped member references;
• keep additional registry types open while requiring block and item registries in tag-bearing PC data.

Test

• focused positive, negative and corruption controls pass;
• the full tools/js suite passes;
• the schema compiles to the generated Tags type;
• duplicate validation adds about 9 ms across the three tested tag artifacts.

Scope

Schema and audit only. No generated tags data or dataPaths changes are included here.

Refs

• Add TagsDataGenerator to supersede obsolete materials.json with modern tag system for multiple Minecraft versions minecraft-data-generator#56
• Add Minecraft pc 1.21.8 tags #1080
• RFC: Tag Schema #463
• Tag schemas #464
• loader: pass tags through to mcData node-minecraft-data#457

[VasilisDragon]

updated this with the finished schema/audit side of the tags work. rebased on current master and all checks are green

[VasilisDragon]

rebased again after master moved; all checks are green

[rom1504]

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

The schema/audit direction matches the current namespaced, open-registry contract in #1308. It checks resolved members, duplicates, canonical ordering, version paths and orphaned files without pretending every custom registry is a closed vanilla enum.

Resolve the current conflicts and deduplicate the shared schema/test registration with #1308, retaining this broader audit and its corruption controls. That is the landing prerequisite; I found no additional schema defect in the reviewed scope and did not rerun the full tag extraction in this publication pass.

Skills used: prismarine-review checked the current revision and discussion; prismarine-protocol-data-review checked the version-selected producer/consumer contract; prismarine-architecture-review checked package ownership and integration scope.