Export moveit_py_utils' cmake target(s)

[rhaschke]

To use moveit_py_utils in downstream projects (e.g. MTC), its targets need to be exported.

[JafarAbdi]

Should we move it to a separate package outside this repo? I needed the same utilities for PickNikRobotics/rviz_visual_tools#239 and my solution was to copy past them

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (2ea784f) 50.51% compared to head (3dc60a0) 50.51%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2207   +/-   ##
=======================================
  Coverage   50.51%   50.51%           
=======================================
  Files         386      386           
  Lines       31736    31736           
=======================================
  Hits        16028    16028           
  Misses      15708    15708           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[rhaschke]

Should we move it to a separate package outside this repo?

Of course, we could provide a MoveIt-independent utility package for python bindings. I thought about this too already.
However, for simplicity, I always decided to stick with a moveit package. In any case, that's a different decision.
For now, we should make moveit_py reusable by downstream packages.

I needed the same utilities for PickNikRobotics/rviz_visual_tools#239 and my solution was to copy past them.

I'm always trying to avoid duplicating code!