ROS-Independent CI

[marip8]

Currently the Linux CI jobs use a custom docker image with ROS1 components installed. This is a bit unnecessary and causes problems for downstream ROS-independent or ROS2 builds that use the docker image generated by tesseract CI (like here). We should update the CI to be independent of ROS as in tesseract-robotics/boost_plugin_loader#12.

[Levi-Armstrong]

What about using colcon but avoid using industrial_ci and ros dependendecies?

[marip8]

Yes, that's what I'm suggesting. That's what we did in the plugin loader library

[marip8]

I recently opened a PR to add this capability to industrial_ci: ros-industrial/industrial_ci#818.

@Levi-Armstrong what do you think about transitioning the builds over to this branch of ICI? It would make the CI builds cleaner and make building downstream CI pipelines for tesseract_ros/2 and other dependent projects easier to do.

[Levi-Armstrong]

I don't have an issue with that. Have you received any feedback on your PR?

[marip8]

Not yet and no comments on the corresponding issue I opened; I'm not sure who to ping for a review

[marip8]

Closing; addressed in #861