feat(autoware_internal_debug_msgs): add MultiArray msgs

[vish0012]

Description

Not applicable.

Effects on system behavior

Not applicable.

Interface changes

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.

[youtalk]

Why don't you use the original ones?

https://github.com/ros2/common_interfaces/blob/master/std_msgs/msg/MultiArrayLayout.msg
https://github.com/ros2/common_interfaces/blob/master/std_msgs/msg/MultiArrayDimension.msg

[cyn-liu]

I am working on task Autoware Universe port to Autoware Core, but this porting guideline requires that each package can only use messages defined under AutowareFoundation GitHub Org (e.g., autoware_msgs and autoware_internal_msgs), And I have noticed that someone has already moved tier4_xxx_msgs to autoware_internal_xxx_msgs, Will we replace the tier4_xxx_msgs in the universe with theautoware_internal_xxx_msgs next?

Why were two messages(ProcessingTimeNode.msg, ProcessingTimeTree.msg) missed when moving to autoware_internal_xxx_msgs, and these two messages are still being used in Autoware.Universe.