Pre-build msg packages with micro-ROS typesupport before full build

[David-LP99]

Problem

The host build (config/host/generic/build.sh) builds the micro-ROS
XRCE-DDS typesupport generators (rosidl_typesupport_microxrcedds_c/_cpp),
sources them, then runs a single full-workspace colcon build.

builtin_interfaces, unique_identifier_msgs, service_msgs, and
action_msgs are pulled in implicitly by rosidl's action/service code
expansion for many interface packages, but those dependent packages don't
declare them in package.xml. As a result, colcon's normal
dependency-ordered build can resolve these four packages from the system
/opt/ros/jazzy install instead of building them in the workspace.

The system versions were built without rosidl_typesupport_microxrcedds_c
available (it's a micro-ROS-only generator, not part of stock ROS 2), so
they have no micro-ROS XRCE-DDS typesupport compiled in. Any package that
needs microxrcedds typesupport for these message types then fails to link.

Fix

• Explicitly pre-build builtin_interfaces, unique_identifier_msgs,
  service_msgs, action_msgs (in that dependency order) after the
  microxrcedds typesupport generators are already on the path, so rosidl
  regenerates and compiles the microxrcedds typesupport for them.
• Re-source install/local_setup.bash afterward so CMAKE_PREFIX_PATH
  prefers these workspace-built versions over /opt/ros/jazzy in the
  subsequent full workspace build.

Testing

• Host build completes without link errors for packages depending on
  action/service interfaces.
• Confirm the resulting install/ typesupport libs for the four
  packages include microxrcedds symbols (not just the system ones).

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[EugenioCollado]

LGTM