feat(planning_test_utils): update test manager for all planning modules

[kyoichi-sugahara]

Description

refactor version of this PR #3076

Related links

Tests performed

Confirmed test success for obstacle_cruise_planner and obstacle_stop_planner.
The test for obstacle_velocity_smoother is commented out as modifications are required on the obstacle_velocity_smoother side.

Node name	Test name	input	output	Exceptional trajectory/route/path_with_lane_id pattern	Current test result	PR
planning_validator	NodeTestWithExceptionTrajectory	trajectory	trajectory	Empty, single point, path with duplicate points	success	#3375
motion_velocity_smoother	NodeTestWithExceptionTrajectory	trajectory	trajectory	Empty, single point, path with duplicate points	Commented out due to fail	#3047
obstacle_cruise_planner	NodeTestWithExceptionTrajectory	trajectory	trajectory	Empty, single point, path with duplicate points	success
obstacle_stop_planner	NodeTestWithExceptionTrajectory	trajectory	trajectory	Empty, single point, path with duplicate points	success
obstacle_velocity_limiter	NodeTestWithExceptionTrajectory	trajectory	trajectory	Empty, single point, path with duplicate points	Commented out due to fail
obstacle_avoidance_planner	NodeTestWithExceptionTrajectory	trajectory	trajectory	Empty, single point, path with duplicate points	Commented out due to fail
scenario_selector	NodeTestWithExceptionTrajectoryLaneDrivingMode NodeTestWithExceptionTrajectoryParkingMode	trajectory	scenario	Empty, single point, path with duplicate points There are 2 patterns of scenarios: LANEDRIVING and PARKING	success	#3376
freespace_planner	NodeTestWithExceptionRoute	route	trajectory	Empty route	success
behavior_path_planner	NodeTestWithExceptionRoute	route	path_with_lane_id	Empty path	Commented out due to fail
behavior_velocity_planner	NodeTestWithExceptionPathWithLaneID	path_with_lane_id	path	Empty path	success

Notes for reviewers

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• I've confirmed the contribution guidelines.
• The PR follows the pull request guidelines.

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

• The PR follows the pull request guidelines.
• The PR has been properly tested.
• The PR has been reviewed by the code owners.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• There are no open discussions or they are tracked via tickets.
• The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.