feat: add software smoke test launch flags

[lblommesteyn]

Problem
For software-only AP1 integration testing, full_system.launch.py can start perception, mapping, planning, and control, but the stack still needs odometry and actuation feedback publishers. Without those, planner/control can stall before hardware is available.

Changes

• Add use_synthetic_odometry launch argument and forward it to mapping_pipeline.launch.py.
• Add use_synthetic_actuation_feedback launch argument.
• Start ap1_control/synthetic_actuation_feedback_node when that flag is enabled.

Example
ros2 launch ap1_bringup full_system.launch.py use_synthetic_odometry:=true use_synthetic_actuation_feedback:=true

Dependencies

• mapping-and-localization#11 provides the synthetic /slam_odom publisher behind use_synthetic_odometry.
• control#12 provides synthetic_actuation_feedback_node.

Test plan

• python3 -m py_compile src/bringup/launch/full_system.launch.py
• git diff --check

[lblommesteyn]

Updated this PR to also add use_synthetic_perception:=true. That forwards to mapping's synthetic perception publisher and disables real YOLO/UFLD for pure software smoke tests. Example now becomes:
os2 launch ap1_bringup full_system.launch.py use_synthetic_perception:=true use_synthetic_odometry:=true use_synthetic_actuation_feedback:=true.

[lblommesteyn]

Verified locally with the software smoke-test command after applying dependent branches locally:
os2 launch ap1_bringup full_system.launch.py use_synthetic_perception:=true use_synthetic_odometry:=true use_synthetic_actuation_feedback:=true. Observed /ap1/mapping/odometer, /ap1/mapping/entities, /ap1/mapping/lanes, /ap1/planning/target_path, /ap1/control/motor_power, and /ap1/control/turn_angle all publish.