Explicitly added current namespace to robot_description_parameter_client

[xmatousm]

We are using LFC and the rest of nodes in a namespace (to be prepared for two robot setup). When LFC is started by ros_control on real hardware, the robot_description_parameter_client_ is created on the correct (same) namespace, requesting the robot_state_publisher server on the same namespace as well, so everything works as expected.

However, when running with gazebo, the LFC itself is correctly started in the requested namespace, but the robot_description_parameter_client_ is created in the root namespace, also requesting the publisher on the root namespace. Seems that there is inconsistencty in ros_gz_sim. The easiest fix to add the current namespace of LFC explicitly.

[nim65s]

Thanks !

[xmatousm]

So how to fix the failing checks?

[nim65s]

we yeet the ros-tooling thing, as I already did few days ago in loco-3d/linear-feedback-controller-msgs#60
Reproducing this here was already on my todo list, so it should be done soon, sorry for the delay and inconvenience.

[nim65s]

Ok, done in #136
Can you rebase your branch on main @xmatousm ?