feat: porting tier4_rtc_msgs from tier4_autoware_msgs to autoware_internal_msgs

[NorahXiong]

Description

Parent issue: autowarefoundation/autoware_core#419

How was this PR tested?

Notes for reviewers

None.

Effects on system behavior

None.

[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.

[NorahXiong]

@mitsudome-r @youtalk Could you please review this PR and enable the CI settings as the preceeding PRs rely on it: https://github.com/autowarefoundation/autoware_core/actions/runs/14569770270/job/40864955684?pr=426

[youtalk]

@mitsudome-r @isamu-takagi @yukkysaito Has the discussion about this porting already been completed? I heard that the RTC needs to be fixed.

[mitsudome-r]

Yes, I will be talking with @takayuki5168 and @yukkysaito sometime this week to discuss about porting of the RTC messages. We should refine it to make it more generic.

[mitsudome-r]

@NorahXiong Sorry, but could you wait a little on working on this task for now?

[NorahXiong]

@NorahXiong Sorry, but could you wait a little on working on this task for now?

Sure. Then I will work on other packages first.

[liuXinGangChina]

hi mits san @mitsudome-r

Any feedback for this msg porting?

[mitsudome-r]

@liuXinGangChina
We might have to refactor the message to be more generic. I have talked with planning team, but we could consider dropping the porting of behavior_velocity_planner_detection_area package from phase 2.