Porting XXXStamped messages from tier4_autoware_msgs to autoware_internal_msgs

[takayuki5168]

Checklist

• I've read the contribution guidelines.
• I've searched other issues and no duplicate issues were found.
• I've agreed with the maintainers that I can plan this task.

Description

Currently, the stamped messages are widely defined in the following directory since the basic built-in messages such as Float32 and String do not have a timestamp field which is very useful for debugging.
https://github.com/tier4/tier4_autoware_msgs/tree/tier4/universe/tier4_debug_msgs/msg

However, they are in the tier4_autoware_msgs, and not officially supported by the autowarefoundation.

Purpose

To officially support the above messages, I would like to propose porting the messages from the tier4_autoware_msgs repository to the autoware_internal_msgs repository.
https://github.com/autowarefoundation/autoware_internal_msgs

Possible approaches

1. copy to autoware_internal_msgs

• feat: add autoware_internal_debug_msgs package autoware_internal_msgs#30
• feat(autoware_internal_debug_msgs): move stamped messages autoware_internal_msgs#31

2. replace messages in autoware.universe and autoware_tools

• BoolStamped.msg
• Int64Stamped.msg
• Float32MultiArrayStamped.msg
• Float32Stamped.msg
• Float64MultiArrayStamped.msg
• Float64Stamped.msg
• Int32MultiArrayStamped.msg
• StringStamped.msg
  • feat(tier4_xxx_rviz_plugin): use StringStamped in autoware_internal_debug_msgs autoware_tools#181
  • feat: use StringStamped in autoware_internal_debug_msgs autoware.universe#9693
• Int32Stamped.msg

3. remove messages in tier4_autoware_msgs

• feat(tier4_debug_msgs): remove stamped messages tier4/tier4_autoware_msgs#157

Definition of done

The above task list is all done.