Make standard attacks configurable per fighter pack

[Swarek]

Problem

Fighter packs configure broad power, speed, and reach values, but individual standard attacks are still generated from a common profile. Advanced fighter authors cannot tune each normal move directly.

Design questions

• Which fields should be configurable without allowing unsafe or unreadable values?
• How should defaults and pack-version migrations work?
• Which competitive invariants should validators enforce?

Acceptance criteria

• Agree on a versioned per-move schema before implementation.
• Preserve current generated defaults for existing packs.
• Support per-move timing, damage, knockback, angle, hitboxes, and movement where appropriate.
• Add validation, migration notes, tests, and a complete example.
• Keep content packs declarative and non-executable.