Add the Mission Measurement: NavigateThroughPoses adapter

[Minipada]

Parent

#305 (mission lifecycle contract), #387 (the NavigateToPose adapter this reuses), and #396 (Ecosystem Measurements epic).

What to build

A sibling dc_measurements plugin, mission_nav2_through_poses
(class MissionNav2ThroughPoses), watching nav2's NavigateThroughPoses action —
the action a deployment issues when a mission is a single job through several
hard-constraint poses in one call, rather than a chain of separate NavigateToPose
goals. Reuses #387's Record schema and ROS-free core logic pattern; the only real
difference is the action interface being watched and the extra fields its
feedback/result carry.

Acceptance criteria

• Action-client wiring against NavigateThroughPoses (configurable action name,
  default navigate_through_poses), following Add the Mission Measurement: nav2 adapter (mission_start/mission_end Records) #387's rclcpp_action pattern
• Emits mission_start/mission_end Records in Add the Mission Measurement: nav2 adapter (mission_start/mission_end Records) #387's schema, with
  mission_type: "navigate_through_poses"
• mission_end carries outcome/reason/error_code/duration_sec/recoveries
  exactly as Add the Mission Measurement: nav2 adapter (mission_start/mission_end Records) #387 defines them, sourced from the equivalent
  NavigateThroughPoses result/feedback fields
• The final waypoint_statuses (which poses in the job succeeded vs. failed) is
  represented on mission_end — implementer's call on exact shape (raw array vs.
  an aggregate count), following whichever is simpler to keep the Record
  reasonably flat; not pre-decided here
• JSON Schema file added for the new Record shape, validated in tests
• Unit tests for the ROS-free interpretation logic, plus a MeasurementServer
  integration test using Add the Mission Measurement: nav2 adapter (mission_start/mission_end Records) #387's fake-action-server test pattern
• Doc page under doc/src/dc/measurements/, matching the convention of
  battery.md/intervention.md

Blocked by

None — can start immediately. Reuses #387's documented Record
schema/pattern and the pre-existing dc_common::StateTransitionDetector
(from #360, already used by intervention/fault), not any code #387 itself
produces — no shared class or header ties the two together, so this doesn't
need #387's implementation to land first.

[Minipada]

Closed via #404 (merged into jazzy).