Enable 24.04 CI, require cmake 3.22.1

[scpeters]

🎉 New feature

Part of gazebosim/gz-cmake#350.

Summary

This adds a GitHub workflow using Noble and increases our minimum required cmake version to 3.22.1 since we are already requiring that in gz-cmake4. I removed one bit of logic for outdated cmake versions in 4925c87.

It also fixes the push branch regex to support multi-digit versions (copied from gazebosim/sdformat#1445) and fixes the CI badges in the README.

Test it

Check CI results

Checklist

• Signed all commits for DCO
• Added tests
• Added example and/or tutorial
• Updated documentation (as needed)
• Updated migration guide (as needed)
• Consider updating Python bindings (if the library has them)
• codecheck passed (See contributing)
• All tests passed (See test coverage)
• While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

[scpeters]

Doxygen check failed on noble:

  ++ curl -s https://raw.githubusercontent.com/gazebosim/gz-cmake/main/tools/doc_check.sh
  Error. The following warnings were found in gz-doxygen.warn.
  warning: source '/github/workspace/build/libgz-rendering-ogre.so' is not a readable file or directory... skipping.
  warning: source '/github/workspace/build/libgz-rendering-ogre.so' is not a readable file or directory... skipping.
  /github/workspace/tutorials/03_rendering_plugins.md:12: warning: Unexpected paragraph command found inside subsection!

moving it back to jammy

[scpeters]

INTEGRATION_load_unload_ogre_gl3plus fails in Noble CI for both Jenkins and GitHub actions

[scpeters]

INTEGRATION_load_unload_ogre_gl3plus fails in Noble CI for both Jenkins and GitHub actions

while reading the console output, I noticed that we don't have ogre-next installed in Noble CI, so I've tried to enable that in 002d504

[scpeters]

INTEGRATION_load_unload_ogre_gl3plus fails in Noble CI for both Jenkins and GitHub actions

while reading the console output, I noticed that we don't have ogre-next installed in Noble CI, so I've tried to enable that in 002d504

I can revert that if we want to address it separately

[iche033]

The tests are failing with undefined symbol issue. I've updated to use the libogre-next-2.3-dev to see if it makes a difference. libogre-next-2.3-dev is version 2.3.1, while libogre-next-dev is 2.3.3

[iche033]

The tests are failing with undefined symbol issue. I've updated to use the libogre-next-2.3-dev to see if it makes a difference. libogre-next-2.3-dev is version 2.3.1, while libogre-next-dev is 2.3.3

ogre2 tests should all pass now. There should only be one ogre1 test failing and there's a workaround in #1033

[iche033]

I'll look into the ogre-next 2.3.3 issue separately

[scpeters]

there are some new gcc warnings, and I'm not sure how to fix them; I'll merge after CI finishes if I don't see any suggestions to resolve them

• https://build.osrfoundation.org/job/gz_rendering-ci-pr_any-noble-amd64/27/gcc/

[iche033]

there are some new gcc warnings, and I'm not sure how to fix them; I'll merge after CI finishes if I don't see any suggestions to resolve them

• https://build.osrfoundation.org/job/gz_rendering-ci-pr_any-noble-amd64/27/gcc/

the compile warnings should be fixed in #1036

[iche033]

I'll look into the ogre-next 2.3.3 issue separately

looks like @j-rivero already reported the issue with the noble's ogre 2.3 debs: https://bugs.launchpad.net/ubuntu/+source/ogre-next/+bug/2063359. So gz-sim / gz-rendering wont work with libogre-next-dev from Ubuntu Noble and instead users have to use lbogre-next-2.3-dev from the osrf repo.