Batch methods: Delete

Rules for AIP-235, covering batch delete methods.

Rule name	Description
`http-body`	Batch Delete methods should use `*` as the HTTP body.
`http-method`	Batch Delete methods must use the POST HTTP verb.
`http-uri-suffix`	Batch Delete methods must have the correct URI suffix
`plural-method-name`	Batch Delete methods must have plural names.
`request-message-name`	Batch Delete methods must have standardized request message names.
`request-names-behavior`	Batch Delete requests should annotate the `names` field with `google.api.field_behavior`.
`request-names-field`	Batch Delete RPCs should have a `names` field in the request.
`request-names-reference`	Batch Delete requests should annotate the `names` field with `google.api.resource_reference`.
`request-parent-field`	Batch Delete RPCs must have a `parent` field in the request.
`request-parent-reference`	Batch Delete requests should annotate the `parent` field with `google.api.resource_reference`.
`request-requests-behavior`	Batch Delete requests should annotate the `requests` field with `google.api.field_behavior`.
`request-unknown-fields`	Batch Delete RPCs should not have unexpected fields in the request.
`response-message-name`	Batch Delete methods must have standardized response message names.
`response-resource-field`	Batch Delete RPCs must have a repeated field for the resource in the response.

Note: Because AIPs sometimes cover topics that have some overlap, some rules related to batch delete methods may be included in the rules for other AIPs.