feat(start_planner): add object_types_to_check_for_path_generation

[kyoichi-sugahara]

Description

In the original implementation, when generating path, a constant distance margin was attempted to be maintained regardless of the object's class. This approach led to a problem where path could not be generated due to the occurrence of objects of an unknown type, even when there were actually no objects exist.

Ideally, we expect that objects of unknown type will not be detected when no objects exist. However, as a short-term measure, we will enable path generation by ignoring specific classes through parameter adjustment.

Please be cautious when setting this parameter to false, as objects of an unknown class might be recognized, and there could actually be objects present.

In the PR description, I'd like to explain the path generation based on the following settings:

When the configuration is set as:

$ ros2 param get /planning/scenario_planning/lane_driving/behavior_planning/behavior_path_planner start_planner.object_types_to_check_for_path_generation.check_car
Boolean value is: True

Conversely, when the setting is adjusted to:

$ ros2 param get /planning/scenario_planning/lane_driving/behavior_planning/behavior_path_planner start_planner.object_types_to_check_for_path_generation.check_car
Boolean value is: False

Tests performed

• PASS TIERIV INTERNAL SCENARIOS

Effects on system behavior

Not applicable.

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.

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.

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

[shmpwk]

LGTM

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 47 lines in your changes are missing coverage. Please review.

Project coverage is 14.78%. Comparing base (92c478e) to head (2ec4bfb).
Report is 1 commits behind head on main.

Files	Patch %	Lines
...behavior_path_start_planner_module/src/manager.cpp	0.00%	42 Missing ⚠️
..._start_planner_module/src/start_planner_module.cpp	0.00%	5 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6370      +/-   ##
==========================================
- Coverage   14.79%   14.78%   -0.01%     
==========================================
  Files        1917     1917              
  Lines      131984   132030      +46     
  Branches    39228    39228              
==========================================
  Hits        19522    19522              
- Misses      90672    90718      +46     
  Partials    21790    21790              

Flag	Coverage Δ		*Carryforward flag
differential	0.00% <0.00%> (?)
total	14.79% <ø> (+<0.01%)	⬆️	Carriedforward from 92c478e

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.