Upgrade wrench to 3.3.1 and regenerate CI job definitions

[LeoUnity]

Summary

Upgrades the wrench recipe engine from 2.3.1 → 3.3.1 and regenerates all Yamato CI job definitions.

• Bumped RecipeEngine.Modules.Wrench to 3.3.1 in Tools/CI/fbxexporter.Cookbook.csproj
• Regenerated all .yamato/wrench/*.yml via dotnet run --project Tools/CI/fbxexporter.Cookbook.csproj (the same command enforced by the test_-_wrench_jobs_up_to_date CI job)

Notable regenerated changes from the 3.x upgrade

• Validation editor track moved 6000.4/staging → 6000.5/staging — please confirm this is the intended validation target
• Local APV tool bumped 1-3-0 → 1-3-3
• Job timeouts raised 10 → 20
• Updated auto-generated header format with # Source: provenance lines

Verification

• Cookbook project builds cleanly against 3.3.1 — no code changes needed in Program.cs/Settings
• Regeneration passed all recipe-engine validation rules (YAM001/YAM002/JOB001), 38 jobs generated
• No remaining 2.3.1 references outside gitignored build artifacts

🤖 Generated with Claude Code

[u-pr]

💡 Harness Review

The regeneration is mostly coherent, but it also changes the release-gating editor matrix in a way that no longer matches the repo's declared test coverage.

The regenerated Wrench jobs silently drop the 6000.4 release line from preview/validation/promotion coverage and replace it with 6000.5, but the source metadata still lists 6000.4 as an active test editor in .yamato/global.metafile. That means release branches can now publish after passing APV/validation only on 6000.0, 6000.3, 6000.5, 6000.6, and 6000.7, with no release-gating job exercising 6000.4 anymore. If 6000.4 is still a supported train, this is a real coverage regression; if it is intentionally retired, the source metadata should be updated in the same PR so the change is explicit and reproducible. Please either reconfigure Wrench to keep generating the 6000.4 jobs or update the repo's source editor matrix to remove 6000.4 deliberately.

_{Reviewed commit e2511b4a}

_{🤖 Helpful? 👍/👎}