Add copper tool speed to the materials speed table (1.21.9+)

[Pix3lPirat3]

getToolSpeed() maps speed from the item-name prefix and had no entry for copper, so every copper tool fell to the 1.0 default in materials.json. Vanilla ToolMaterial.COPPER is 5.0. Add it for the modules that have copper tools: 1.21.9, 1.21.10, 1.21.11 and 26.1.

MaterialsDataGenerator.getToolSpeed() derives a tool's speed from its name prefix through a fixed table that predates copper tools, so from 1.21.9 every copper tool is emitted at the 1.0 default. Vanilla ToolMaterial.COPPER is 5.0 (new ToolMaterial(INCORRECT_FOR_COPPER_TOOL, 190, 5.0F, ...) in 1.21.9 and 26.1). With shipped data, prismarine-block digTime() reports a copper pickaxe on stone at 2300 ms instead of 450 ms, and a copper axe on oak log at 3000 ms instead of 600 ms.

This adds copper to the table for the four modules whose registry has copper tools. Regenerating them changes exactly 16 materials.json entries per version - every copper tool, 1.0 -> 5.0 — and nothing else. Live on a vanilla 26.1 server with mineflayer 4.39.0, copper pickaxe on stone breaks in 453 ms (was 2307), on iron ore in 902 ms (was 4563).

[rom1504]

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

Looks ready to merge for the copper-speed correction. All four affected-version generation jobs pass. I checked the exact-head 1.21.9 and 26.1 CI artifacts against data#1309: the entire materials tables match; the data change is exactly 16 copper entries per version, from 1 to 5. With the candidate data, prismarine-block reports copper pickaxe/stone 450 ms, shovel/dirt 150 ms and axe/oak log 600 ms.

The corresponding data already landed as part of minecraft-data#1310, so this producer fix is still needed to preserve it on regeneration. Generator#88 includes the same copper change; coordinate those two overlapping branches when landing. An unrelated 1.18 CI job was cancelled; I did not perform a new local Java run.

Skills used: prismarine-protocol-data-review connected exact producer artifacts to the released-data direction and real model; prismarine-architecture-review checked the bounded fix in the existing tier table; prismarine-review checked actual base/head and cross-PR overlap.

[rom1504]

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

The copper-speed producer fix still matches the reviewed native value and downstream dig-time behavior in the existing review. Its data is already included in minecraft-data #1310, and generator #88 contains this same fix.

The refreshed Build 1.18 job is failed, so diagnose/rerun that remaining integration check rather than treating the full matrix as cleared. I found no new defect in the copper mapping. Coordinate the overlapping #88 branch when landing; no new local Java or live-server run was performed.

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.