feat(vehicle_cmd_gate): add multiple pause source ability

[brkay54]

Description

Before this be merged, msg file should be merged.
tier4/tier4_autoware_msgs#82

🤖 Generated by Copilot at 8030a11

Summary

✨♻️📝

Improved the pause interface for the vehicle command gate by allowing multiple sources of pause requests and publishing the pause state. Refactored the PauseInterface class and added a new method update_pause_state to handle the pause logic. Modified pause_interface.cpp and pause_interface.hpp accordingly.

We are the masters of the pause interface
We control the sources of the halt
We update and publish the state of grace
We defy the forces of default

Walkthrough

• Add a feature that allows multiple sources to request a pause of the vehicle command gate, and shows which sources are requesting it (link, link, link, link, link)
• Modify the constructor of the PauseInterface class to initialize the pause_state_ message and remove the is_paused_ and prev_is_paused_ variables (link)
• Modify the publish method to use the pause_state_ and pause_map_ variables, and call the update_pause_state method before publishing (link)
• Modify the on_pause callback to store the pause request and the source in the pause_map_ variable, and call the update_pause_state method (link)
• Add the update_pause_state method that updates the pause_state_ message based on the pause_map_ variable (link, link)
• Add the pause_state_, pause_map_, and prev_pause_map_ variables to the PauseInterface class, and remove the is_paused_ and prev_is_paused_ variables (link)
• Include the header file for the unordered_map container in the pause_interface.hpp file (link)

Related links

Tests performed

Notes for reviewers

Interface changes

After this PR, requests should include the node's name.

Effects on system behavior

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.