Add CI Pipeline #28
Description
Currently we have 4 branches, 2 for development of ros1/ros2 and 2 master branches.
While the maintaining ROS2 distribution is Humble, we should also make sure (or at least check) that also other distributions are supported (see #27).
Therefore a CI pipeline would be helpful to automatically test and validate the code for different setups.
Also to ensure the already prepared code formatting/style is complied.
The setup of a CI includes the following tasks:
- setup CI to automatically trigger at push or PR
- define different environments to test (multiple ROS(2) distributions
- execute the build process (and optional tests)
- ensure compliance of code formatting
- add CI status badge to README