Part of #1346

Summary

Introduce a "list crew template" model which is many-to-one to a List. It stores crew name and setup options for how a crew is selected.

Requirements

Model

• Many-to-one relationship to List
• Stores crew name
• Stores selection methodology, starting with:
  • Specific fighters from the list (M2M to ListFighter)
  • N randomly selected fighters (from those not otherwise chosen)

UI

• CRUD interface similar to existing print configs
• Accessible from the main list UI
• Management table showing all templates for a list

Constraints

• Only fighters whose state is "Active" should be eligible for selection
• Random rerolls are not permitted once a crew is materialised (this is relevant in chunk 2 but affects template design)

Considerations

• Template design should support future selection methods (e.g., 3 chosen + 1D3 random)
• Consider how the template stores the "N random" configuration (integer field for count)