Bumps in jetty: use gz-gui10

[azeey]

See gazebo-tooling/release-tools#1235

[j-rivero]

Remove Jammy as supported CI in 066aca9

[azeey]

Thanks! We really need to complete gazebo-tooling/release-tools#1222 and forward port the changed. Otherwise, we won't have linters and code coverage on any of the Jetty branches.

[azeey]

@osrf-jenkins run tests please

[azeey]

The Noble build is failing with the following error

#7 https://api.github.com/repos/gazebo-tooling/gzdev/git/refs/heads/ci_matching_branch/bump_jetty_gz-sim10
#7 ERROR: invalid response status 404

#8 [ 2/34] RUN echo 'export DEBIAN_FRONTEND=noninteractive' >> /root/.bashrc
#8 CACHED

#9 [ 3/34] RUN echo 'APT::Get::Never-Include-Phased-Updates "true";' > /etc/apt/apt.conf.d/90-phased-updates
#9 CACHED

#10 [ 4/34] RUN echo "deb http://archive.ubuntu.com/ubuntu noble-security main restricted universe multiverse" &&                                                      >> /etc/apt/sources.list
#10 CACHED

#11 [ 5/34] RUN apt-get  update &&     apt-get install -y dirmngr git python3 python3-docopt python3-yaml python3-distro
#11 CACHED

#12 [ 6/34] ADD https://api.github.com/repos/gazebo-tooling/gzdev/git/refs/heads/master version.json
#12 CACHED

#13 [ 7/34] RUN rm -fr /root/gzdev     && git clone /~https://github.com/gazebo-tooling/gzdev -b master /root/gzdev
#13 CACHED

#5 [internal] load build context
#5 CANCELED
------
 > https://api.github.com/repos/gazebo-tooling/gzdev/git/refs/heads/ci_matching_branch/bump_jetty_gz-sim10:
------
ERROR: failed to solve: failed to load cache key: invalid response status 404

@j-rivero , @scpeters any clue why? Is the ci_matching_branch required on the gzdev branch?