Update Gazebo ROS vendor packages to point to the new stable branches

[azeey]

Configuration

• release: jetty

Process

• Jetty support: bump to 5.0.0, fix package names gazebo-release/gz_cmake_vendor#16
• Jetty support, 7.0.0-pre1 gazebo-release/gz_common_vendor#15
• Jetty support, 11.0.0-pre1 gazebo-release/gz_fuel_tools_vendor#10
• Jetty support, 10.0.0-pre1 gazebo-release/gz_gui_vendor#6
• Jetty support, 9.0.0-pre1 gazebo-release/gz_launch_vendor#6
• Jetty support: bump to 9.0.0, fix package names gazebo-release/gz_math_vendor#12
• Jetty support, 12.0.0-pre1 gazebo-release/gz_msgs_vendor#9
• Jetty support, 9.0.0-pre1 gazebo-release/gz_physics_vendor#12
• Jetty support, 4.0.0-pre1 gazebo-release/gz_plugin_vendor#7
• Jetty support, 10.0.0-pre1 gazebo-release/gz_rendering_vendor#11
• Jetty support, 10.0.0-pre1 gazebo-release/gz_sensors_vendor#9
• Jetty support, 10.0.0-pre1 gazebo-release/gz_sim_vendor#14
• Jetty support: minor updates gazebo-release/gz_tools_vendor#9
• Jetty support, 15.0.0-pre1 gazebo-release/gz_transport_vendor#11
• Jetty support: bump to 4.0.0, fix package names gazebo-release/gz_utils_vendor#11
• Jetty support: bump to 16.0.0, fix package names gazebo-release/sdformat_vendor#16

[scpeters]

I've started opening pull requests to update the vendor packages for Jetty. Since the vendor packages currently only look for a tag in the upstream repository, I've added a VENDOR_FROM_LIB_VCS_REF cmake option to allow the vendoring to be done from a vcs ref (main by default). I've been adding the pull requests to the issue description above.

[scpeters]

I've been testing this in a colcon workspace with the packages specified in the following repos file:

• https://gist.github.com/scpeters/45c203457ae9c9a402f8d9b6b4fcc45b

I've tested up to gz_math_vendor with the following command:

colcon build --packages-up-to gz_math_vendor --cmake-args -DVENDOR_FROM_LIB_VCS_REF=ON