Takagi, Isamu

I think we need rules to clarify the interface for the following reasons. - It's often difficult to know what parameters/topic the node has because the interface definitions (e.g. create_subscription)...

I'll split the PR.

This PR is ready.

@yukkysaito I think that it will be unified with the `snake_case` https://github.com/autowarefoundation/autoware.universe/pull/1429#discussion_r932328837. I'll auto format later.

> How to make the car stop slowly when the localization fails.(the current localization error monitoring module does not notify other modules to take emergency action after the localization failure.)...

@taikitanaka3 @tkhmy What is side shift? Is it a lateral distance of lane change or avoidance?

So the other factors (e.g. intersection) does not have an side shift value. I think there are two ways for this. - Convert to JSON and use detail field. -...

Add message readme. https://github.com/autowarefoundation/autoware.universe/pull/1500/commits/8107b29b4d1c98481461687fcade986c8787221a

@kenji-miyake @yukkysaito @mitsudome-r [In this PR](https://github.com/autowarefoundation/autoware.universe/pull/1559), we changed the route topic name to `/planning/mission_planning/route` (the first name was `/planning/routing/route`). However, an error has occurred because the name is already used...

@kenji-miyake The existing topic is an implementation-dependent message type [HADMapRoute](https://github.com/tier4/autoware_auto_msgs/blob/tier4/main/autoware_auto_planning_msgs/msg/HADMapRoute.idl). The new topic is an implementation-independent API message type [Route](https://github.com/autowarefoundation/autoware.universe/blob/main/common/autoware_ad_api_msgs/routing/msg/Route.msg). So it cannot be replaced without forcing the internal implementation...