Bless vector as a Destination type

[Minipada]

Parent

#440

What to build

In the fleet topology a robot's only Records Destination is the edge aggregator — another
Shipper. That Destination type is not blessed, so today it can only be configured as
passthrough: hand-written TOML that DC does not parse or validate. A typo means the robot
silently ships nowhere, which is the exact failure the buffering design exists to prevent.

Bless vector as a Destination type alongside postgres, s3, file and console, with
the same ROS-param surface and the same startup-time validation.

Acceptance criteria

• vector is accepted as a Destination type, configured entirely from ROS parameters
• Invalid configuration (missing address, out-of-range port) fails at startup with a clear, attributable error
• The rendered Shipper config forwards the Destination's Tags to the configured address
• Records reach a second Shipper acting as an aggregator, verified end to end
• Passthrough remains available and unchanged for every other sink type
• Covered by dc_bridge's existing render tests, alongside the other blessed types

Blocked by

• None — can start immediately

[Minipada]

Merged into jazzy via #455. Not auto-closed because #455 merged into jazzy, not this repo's default branch (humble).