refactor(component_state_monitor): replace topic state monitor by behavior path planner timeout

[takam5f2]

Description

Remove topic_state_monitor-based diagnostic entries that are now redundant, because behavior_path_planner internally monitors its input message timeouts (see autowarefoundation/autoware_universe#12075).

The following topic_state_monitor entries are removed from component_state_monitor config:

Domain	Removed topic_state_monitor	Reason
localization	pose_twist_fusion_filter	Monitored as odometry input by behavior_path_planner
map	vector_map	Monitored as vector map input by behavior_path_planner
perception	traffic_signals	Monitored as traffic signal input by behavior_path_planner
perception	objects	Monitored as perception objects input by behavior_path_planner
perception	pointcloud	Monitored as obstacle segmentation input by behavior_path_planner
planning	route	Monitored as route input by behavior_path_planner

How was this PR tested?

Setup before launch

cd /path/to/autoware
source install/setup.bash

cd /path/to/autoware/src/launcher/autoware_launch
gh pr checkout 1779 --repo autowarefoundation/autoware_launch

Launch Autoware with PSim.

source ~/autoware/install/setup.bash
ros2 launch autoware_launch planning_simulator.launch.xml map_path:=$HOME/autoware_map/sample-map-planning vehicle_model:=autoware_sample_vehicle sensor_model:=autoware_sample_sensor_kit

Run converter_node from diagnostic_graph_utils package.

ros2 run autoware_diagnostic_graph_utils converter_node

Run rqt_runtime_monitor

 ros2 run rqt_runtime_monitor rqt_runtime_monitor --ros-args -r diagnostics:=diagnostics_array

You'll find that /autoware/planning/behavior_path_planner/incoming_message_timeout is defined.

Notes for reviewers

None.

Effects on system behavior

Some topic_state_monitor will not run after this changes.

[github-actions]

Thank you for contributing to the Autoware project!

🚧 If your pull request is in progress, switch it to draft mode.

Please ensure:

• You've checked our contribution guidelines.
• Your PR follows our pull request guidelines.
• All required CI checks pass before marking the PR ready for review.

[isamu-takagi]

Could you keep it as an empty file to minimize the differences with the fork repository?

[takam5f2]

@isamu-takagi
Thank you for your feedback.

I have restored the perception.yaml file at 067887c.

I changed the percetion.yaml to let /autoware/perception notify ok always to clafiry the difference.
Do you think whether the change is acceptable?