Disable use_intra_process_comms in servo launch files

[tylerjw]

Description

This is a fix for Rolling as enabling this causes the component container to die with this error:

[ERROR] [test_servo_integration_container]: Component constructor threw an exception: intraprocess communication is not allowed with a zero qos history depth value

Note there was also a typo in servo_launch_test_common.py (missing a s).

On the changes in servo_example.launch.py. Even if we could enable it for the two components it is enabled for it is a major pessimization to enable it for only some of the nodes within a container.

Checklist

• Required by CI: Code is auto formatted using clang-format
• While waiting for someone to review your request, please help review another open pull request to support the maintainers

[codecov]

Codecov Report

Merging #722 (e7e8f92) into main (26a2ab7) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #722      +/-   ##
==========================================
- Coverage   54.23%   54.21%   -0.01%     
==========================================
  Files         192      192              
  Lines       20224    20224              
==========================================
- Hits        10966    10963       -3     
- Misses       9258     9261       +3     

Impacted Files	Coverage Δ
...nning_scene_monitor/src/planning_scene_monitor.cpp	45.31% <0.00%> (-0.50%)	⬇️
...e/collision_detection_fcl/src/collision_common.cpp	74.64% <0.00%> (+0.25%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 26a2ab7...e7e8f92. Read the comment docs.

[vatanaksoytezer]

We should also change the ones in tests as well: https://github.com/ros-planning/moveit2/blob/main/moveit_ros/moveit_servo/test/launch/servo_launch_test_common.py#L150 Sorry my bad.

[henningkayser]

You should probably remove this warning, also. Do we even have a history depth of 0? Should we enforce something else in the profile and suggest enabling intra process comms on all components?

[tylerjw]

Somewhere in moveit (I'm assuming) we do have a history depth of 0 for some topic and that is the cause of this.