Catching up to tesseract_ros

[marrts]

With #33 most of the functionality is there, but there are a few differences or changes that need to be made to fully catch up.

• [x] Topic fields in the workbench don't actually look up ROS topics, they just take string inputs
• [ ] Can't run waitForInput() when running from a launch because of how ROS 2 interfaces with the terminal, an alternative should be proposed, or we can just choose to drop this
• [ ] Manipulation widget does not work in the workbench, for some reason we are unable to move around the manipulation objects, but we can change numbers to move the robot to different positions, it is just less efficient
• [x] tesseract_rviz causing a build issue when rebuilding
• [ ] If you want to load the URDF/SRDF into RVIZ as parameters you need to launch RVIZ node with those parameters declared, again this is more of a difference between ROS and ROS 2 than a tesseract thing
• [x] Currently tesseract_rviz uses boost::shared_ptrs everywhere because that's what ROS 1 rviz did, but ROS 2 uses std::shared_ptrs so we should probably update to match
• [x] The planning server itself isn't yet ported

[marrts]

@smith-doug did we resolve the tesseract_rviz building issue, I can't remember?

[smith-doug]

Here https://github.com/marrts/tesseract_ros2/pull/1

[rjoomen]

I made a PR to the repo of @marrts.

This includes fixes for the first (ROS topics) and the before-last (boost) points in the list above.

[Levi-Armstrong]

@marrts can this be closed?

[rjoomen]

No, some issues are still open, I think. I suggest to check the points that are done though.

[marrts]

Checked off the issues resolved by @rjoomen

[rjoomen]

@Levi-Armstrong I think the point about the manipulation widget can be closed, as it seems to work the same as tesseract_ros1 now, right? Then we could close the entire issue, as the other two points can't be fixed.

[Levi-Armstrong]

Sound good.