Update control_msgs to use humble-devel branch for humble and newer

[tfoote]

@bmagyar @christophfroehlich

I was looking at a compliance process and found that ros-controls/control_msgs#114 wasn't available in the devel branch and saw that it was pointing all the way back to foxy. When there was a humble backport here: ros-controls/control_msgs#116

Based on this humble backport I'm assuming that humble is the appropriate development branch for humble and also iron, where rolling is on master.

[tfoote]

On review humble does come from humble in bloom: https://github.com/ros2-gbp/control_msgs-release/blob/ddb3f67f899cd1a7e4b88c086a51ef9718aa2a6f/tracks.yaml#L182

Iron is currently on master though so switching: https://github.com/ros2-gbp/control_msgs-release/blob/ddb3f67f899cd1a7e4b88c086a51ef9718aa2a6f/tracks.yaml#L250

[christophfroehlich]

Thanks for this update!
I was wondering these days why the api docs on docs.ros.org are not present for humble/iron, but this could explain it. Is the docs job started automatically or can we trigger that?
https://build.ros2.org/job/Idoc__control_msgs__ubuntu_jammy_amd64/lastBuild/
https://build.ros2.org/job/Hdoc__control_msgs__ubuntu_jammy_amd64/

[tfoote]

The doc job should reconfigure overnight with the new branch and then run on the next polling cycle detecting the content, which I think is every 3 days right now.

[christophfroehlich]

great, thanks!

[bmagyar]

Perfect, thank you!