docs: group generated tag test options with headings (#41612)

As tag test generation has expanded across the provider, the number of parameters which can be passed to the tags test annotation has grown significantly. Given the number of options, the contributor documentation on this section has become difficult to read in its entirety. This change bundles the various parameters into related groups and adds headings to break up the available options into smaller standalone sections.

Author: jar-b

docs/resource-tagging.md

@@ -472,6 +472,8 @@ If a resource or data source type supports tags but does not use transparent tag
 
 Additional `@Testing(...)` parameters can be used to control the generated tests.
 
+##### Required Argument parameters
+
 Most testing configurations take a single parameter, often a name or a domain name.
 The most common case is parameter `rName` with a value generated by `sdkacctest.RandomWithPrefix(acctest.ResourcePrefix)`, so this is the default.
 If no `rName` is required, add the annotation `@Testing(generator=false)`.
@@ -495,6 +497,8 @@ and sets the annotation `@Testing(tlsKeyDomain=rName)` to reference it.
 No additional parameters can be defined currently.
 If additional parameters are required, and cannot be derived from `rName`, the resource type must use manually created acceptance tests as described below.
 
+##### Exists and Destroy parameters
+
 Most `Exists` functions used in acceptance tests take a pointer to the returned API object.
 To specify the type of this parameter, use the annotion `@Testing(existsType=<reference>)`.
 This references a Go type and package path with optional package alias, using the format
@@ -508,6 +512,11 @@ For example, the S3 Object uses
 Some services or resource types are using a new variant of the standard `Exists` and `DestroyCheck` functions that use `acctest.ProviderMeta` internally, and thus take a `testing.T` as a parameter.
 In that case, add the annotations `@Testing(existsTakesT=true)` and `@Testing(destroyTakesT=true)`, respectively.
 
+Some resource types use the no-op `CheckDestroy` function `acctest.CheckDestroyNoop`.
+Use the annotation `@Testing(checkDestroyNoop=true)`.
+
+##### Import parameters
+
 The generated acceptance tests use `ImportState` steps.
 In most cases, these will work as-is.
 To ignore the values of certain parameters when importing, set the annotation `@Testing(importIgnore="...")` to a list of the parameter names separated by semi-colons (`;`).
@@ -517,29 +526,36 @@ If the identifier can be retrieved from a specific resource attribute, use the a
 If the identifier can be retrieved from a `resource.ImportStateIdFunc`, use the annotation `@Testing(importStateIdFunc=<func name>)`.
 If the resource type does not support importing, use the annotation `@Testing(noImport=true)`.
 
-If the tests need to be serialized, use the annotion `@Testing(serialize=true)`.
+##### Serialization parameters
+
+If the tests need to be serialized, use the annotation `@Testing(serialize=true)`.
 If a delay is needed between serialized tests, also use the annotation `@Testing(serializeDelay=<duration>)` with a duration in the format used by [`time.ParseDuration()`](https://pkg.go.dev/time#ParseDuration).
 For example, 3 minutes and 30 seconds is `3m30s`.
 
+##### Empty and Null Tag parameters
+
 Some services do not support tags with an empty string value.
 In that case, use the annotation `@Testing(skipEmptyTags=true)`.
 
 Some services do not support tags with an null string value.
 In that case, use the annotation `@Testing(skipNullTags=true)`.
 
-Some resource types use the no-op `CheckDestroy` function `acctest.CheckDestroyNoop`.
-Use the annotation `@Testing(checkDestroyNoop=true)`.
+##### Tag Update parameters
 
 For some resource types, tags cannot be modified without recreating the resource.
 Use the annotation `@Testing(tagsUpdateForceNew=true)`.
 
 Resource types which pass the result of `getTagsIn` directly onto their Update Input may have an error where ignored tags are not correctly excluded from the update.
 Use the annotation `@Testing(tagsUpdateGetTagsIn=true)`.
 
+##### Resource Identifier parameters
+
 Some tests read the tag values directly from the AWS API.
 If the resource type does not specify `identifierAttribute` in its `@Tags` annotation, specify a `@Testing(tagsIdentifierAttribute=<attribute name>)` annotation to identify which attribute value should be used by the `listTags` function.
 If a resource type is also needed for the `listTags` function, also specify the `tagsResourceType` annotation.
 
+##### Tag Removal parameters
+
 At least one resource type, the Service Catalog Provisioned Product, does not support removing tags.
 This is likely an error on the AWS side.
 Add the annotation `@Testing(noRemoveTags=true)` as a workaround.