Test ROS 2 release jobs in CI

[cottsay]

Part of this change is getting the RPM jobs to work with the release script. The other is simply a matter of listing the jobs in the workflow.

[cottsay]

Looking into the RPM job seems like there are errors in the building

These are test errors, not build errors. Just like with the debs, the RPM build will try to run any tests it finds after finishing the build. Unfortunately, our approach to testing by targeting all of the contents of the source directory recursively is clashing with the standard RPM build model wherein the "build" directory is created as a unique subdirectory in the source tree. So we almost always have linter failures, because the generated files almost never conform.

[cottsay]

Unfortunately, our approach to testing by targeting all of the contents of the source directory recursively is clashing with the standard RPM build model wherein the "build" directory is created as a unique subdirectory in the source tree. So we almost always have linter failures, because the generated files almost never conform.

Follow-up mitigation for this: ros-infrastructure/bloom#647