Expand mission objective parameters by mission type

[jackandcarter]

Motivation

• Replace generic objective fields with per-mission parameters so each mission type can be tuned independently.
• Ensure mission controllers read the correct mission-specific targets and radii instead of a shared hazardCount/exitRadius value.
• Surface missing or invalid objective parameters at editor time to prevent runtime misconfiguration when generating mission UI.
• Add documentation guidance so authors remember to review per-mission objective parameters when tuning missions.

Description

• Added new per-mission fields and accessors to MissionObjectiveParameters (e.g. AsteroidMiningOreTarget, CriticalDemolitionTargetCount, DebrisNavigationHazardCount, DebrisNavigationExitRadius, HazardNeutralizationHazardCount).
• Updated AsteroidMiningMissionController, CriticalDemolitionMissionController, DebrisNavigationMissionController, and HazardNeutralizationMissionController to consume the new per-mission parameters instead of the old generic fields.
• Implemented ValidateObjectiveParameters(MissionDefinition) in MissionUIGeneratorWindow and hooked it into PostProcessMissionSetup to report missing or invalid objective values during UI generation.
• Updated Assets/Docs/M2EditorTools.md to call out reviewing mission objective parameters as part of the authoring guidelines.

Testing

• No automated tests were executed for these changes.

---

Codex Task