feat(ad-api): add restrictions and options

[isamu-takagi]

Description

Add restrictions and options for safety. Related to autowarefoundation/autoware_adapi_msgs#61.
See the release notes for v1.6.0 for details.

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

[github-actions]

Documentation URL: https://autowarefoundation.github.io/autoware-documentation/pr-602/
Modified URLs:

• https://autowarefoundation.github.io/autoware-documentation/pr-602/design/autoware-interfaces/ad-api/features/routing/
• https://autowarefoundation.github.io/autoware-documentation/pr-602/design/autoware-interfaces/ad-api/list/api/routing/clear_route/
• https://autowarefoundation.github.io/autoware-documentation/pr-602/design/autoware-interfaces/ad-api/list/api/vehicle/doors/command/
• https://autowarefoundation.github.io/autoware-documentation/pr-602/design/autoware-interfaces/ad-api/list/api/vehicle/status/
• https://autowarefoundation.github.io/autoware-documentation/pr-602/design/autoware-interfaces/ad-api/release/
• https://autowarefoundation.github.io/autoware-documentation/pr-602/design/autoware-interfaces/ad-api/types/autoware_adapi_v1_msgs/msg/RouteOption/

[youtalk]

The current autoware_adapi_msgs version is v1.3.0. https://github.com/autowarefoundation/autoware_adapi_msgs/tags
So v1.4.0 seems to be better to bump up, doesn't it?

Suggested change

	**[v1.6.0]** This option only affects the route change APIs. Autoware accepts new route even while the vehicle is using the current route. The APIs fail if it cannot safely transition to new route. When set false, the APIs always fail when the vehicle is using the route.
	**[v1.4.0]** This option only affects the route change APIs. Autoware accepts new route even while the vehicle is using the current route. The APIs fail if it cannot safely transition to new route. When set false, the APIs always fail when the vehicle is using the route.

[isamu-takagi]

@youtalk
Your comment made me realize that there are two versions of the AD API: specification and messages. Since we are talking about the specification version here, v1.6.0 is correct. Because the specification version v1.5.0 has already been released.

I think it's necessary to create a correspondence table between specification and message versions, or to update the message version to match the specifications version even if there are no message changes. Which do you think is better?

[youtalk]

update the message version to match the specifications version even if there are no message changes.

I think it is more clear. Please update package.xml to bump version to 1.6.0 even there is no actual updates by next PR.