Moveit2 python bindings parsing correct config to UR robot

[Mennosytsma]

I see that issue #2014 is closed, but the proposed solutions combined with my basic knowledge make that I still cannot reach the initial goal the title suggests.
Based on the previous discussions I wanted to proceed with the files @cpr-fer linked to, which resulted in the package here.
I have changed the joint names in motion_planning_python_api_tutorial.py to match the UR (the values in the python script are still referencing to panda, but if it gets the right descriptions that should not be an issue, hope to fix that later)
I also preferred the method of @cpr-fer to make only minor changes to the original ur_moveit.launch.py, but I think this results in not enough information in the moveit_config dict, as I get the following error when it runs plan_result = planning_component.plan()

[WARN] [1698332153.851265890] [moveit.ompl_planning.planning_context_manager]: Cannot find planning configuration for group 'ur_manipulator' using planner 'RRTConnectkConfigDefault'. Will use defaults instead.
[WARN] [1698332153.851414927] [moveit.ompl_planning.model_based_planning_context]: It looks like the planning volume was not specified.
[INFO] [1698332153.851589965] [moveit.ompl_planning.model_based_planning_context]: Planner configuration 'ur_manipulator' will use planner 'geometric::RRTConnect'. Additional configuration parameters will be set when the planner is constructed.
[WARN] [1698332153.903266767] [moveit.ros_planning.planning_pipeline]: The planner plugin did not fill out the 'planner_id' field of the MotionPlanResponse. Setting it to the planner ID name of the MotionPlanRequest assuming that the planner plugin does warn you if it does not use the requested planner.

The resulting robot trajectory has a duration of 0, which indicated to me that something went wrong in the planning, but it is not clear to me what more parameters I need to add to the moveit_py node to get the interface to work correctly.

Testing environment
To test this code I make use of Ubuntu 22, ROS2 Rolling and UR ros2 driver and description

Next to running test_moveitpy.launch with the argument ur_type:=ur5 I run the default ur_control launch file in a separate terminal and have a ur5 simulated in docker that runs external control, dragging and planning a path using RVIZ works perfectly fine, but the tutorial does not work yet

Originally posted by @Mennosytsma in #2014 (comment)

[Mennosytsma]

I managed to find a solution for my problem, described in This new issue.