feat(logpacker): add rosbag recoding api

[ito-san]

Related Links

TIER IV INTERNAL SLACK

Description

The request command should use ROS2 service instead of topic, and the status should be exchanged in numerical format rather than in string.

Changes

• Request to start/stop rosbag recording
  • /bagpacker/record std_msgs/Bool has been discontinued.
  • Replace this with /api/autoware/set/rosbag_record tier4_external_api_msgs::srv::SetRosbagRecord
• Status of rosbag recoding
  • /bagpacker/state std_msgs/msg/String has been discontinued.
  • Replace this with /api/autoware/get/rosbag_record_status tier4_external_api_msgs::msg::RosbagRecordStatus
• Status of whether the ros2 bag record command is currently running or not.
  • /bagpacker/condition std_msgs/Bool has been discontinued since this duplicates the above.

Remarks

Pre-Review Checklist for the PR Author

PR Author should check the checkboxes below when creating the PR.

• Code is properly formatted
• Assign PR to reviewer

Checklist for the PR Reviewer

Reviewers should check the checkboxes below before approval.

• Commits are properly organized and messages are according to the guideline
• Code is properly formatted
• PR title describes the changes

Post-Review Checklist for the PR Author

PR Author should check the checkboxes below before merging.

• All open points are addressed and tracked via issues or tickets
• Write release notes

CI Checks

• Build and test for PR: Required to pass before the merge.
• Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

[0x126]

LGTM

[tsugi1203]

LGTM

[tkimura4]

LGTM

[yabuta]

LGTM

[mitsudome-r]

Memo:

• I would like to have confirmation with the topic names for /api/autoware/set/rosbag_record and /api/external/get/rosbag_record_status to see if they should share the same namespace or not. (This can be discussed when we make the changes to logpacker)
• Please update the documentation for TIER IV API page https://github.com/tier4/autoware-documentation (https://tier4.github.io/autoware-documentation/tier4-main/design/autoware-interfaces/prototyping/) so that we can track the usecase of this new service and message.
• (cc. @yukkysaito ) We should consider refactoring tier4_api_msgs and tier4_external_api_msgs . Depending on the discussion we might have to change the package name (so the namespace of the message in the code) later.

[yabuta]

LGTM

[ito-san]

@mitsudome-r

/api/autoware/set/rosbag_record and /api/external/get/rosbag_record_status

The namespace should be shared and it should be /api/autoware. I made changes to the description.

[ito-san]

@mitsudome-r

documentation for TIER IV API page

Filed a new PR, please see tier4/autoware-documentation#44.