TPP Server

[marip8]

This PR introduces a tool path planning server that runs a tool path planning pipeline based on the YAML configuration input and specified mesh resource and returns the set of planned tool paths.

[DavidSpielman]

Should this package be renamed to noether_ros2 to avoid ambiguity with ROS1 and match how our other ROS2 interfaces (i.e. industrial_calibration_ros2) are named?

[marip8]

The repository itself is named noether_ros2, but the package is called noether_ros to align with other ROS-Industrial projects that support both ROS1 and ROS2. For example, the packages in industrial_calibration_ros and industrial_calibration_ros2 are both called industrial_calibration_ros. This is the same for other packages like reach_ros/reach_ros2 and pcl_ros in perception_pcl.

The intent is to make end-user transitions from ROS1 to ROS2 less painful by not requiring a name change from <package_name>_ros to <package_name>_ros2. It also makes it easier to port a repo from ROS1 to ROS2 (or vice versa) because you don't have to find-replace all the places where the name is used

[DavidMerzJr]

I only found one or two real issues. Some stylistic comments/questions/suggestions. Would like to hear your responses to some of these. Great job putting this together!

[DavidMerzJr]

Two small things left, otherwise looks great.