feat(dlp): update the api

#### dlp:v2

The following keys were added:
- schemas.GooglePrivacyDlpV2InfoType.properties.version.type (Total Keys: 1)

Author: yoshi-automation

docs/dyn/dlp_v2.organizations.deidentifyTemplates.html

@@ -104,6 +104,7 @@ <h3>Method Details</h3>
     { # Configuration for determining how redaction of images should occur.
       &quot;infoType&quot;: { # Type of information detected by the API. # Only one per info_type should be provided per request. If not specified, and redact_all_text is false, the DLP API will redact all text that it matches against all info_types that are found, but not specified in another ImageRedactionConfig.
         &quot;name&quot;: &quot;A String&quot;, # Name of the information type. Either a name of your choosing when creating a CustomInfoType, or one of the names listed at https://cloud.google.com/dlp/docs/infotypes-reference when specifying a built-in type. When sending Cloud DLP results to Data Catalog, infoType names should conform to the pattern `[A-Za-z0-9$-_]{1,64}`.
+        &quot;version&quot;: &quot;A String&quot;, # Optional version name for this InfoType.
       },
       &quot;redactAllText&quot;: True or False, # If true, all text found in the image, regardless whether it matches an info_type, is redacted. Only one should be provided.
       &quot;redactionColor&quot;: { # Represents a color in the RGB color space. # The color to use when redacting content from an image. If not specified, the default is black.
@@ -153,6 +154,7 @@ <h3>Method Details</h3>
         &quot;exclusionType&quot;: &quot;A String&quot;, # If set to EXCLUSION_TYPE_EXCLUDE this infoType will not cause a finding to be returned. It still can be used for rules matching.
         &quot;infoType&quot;: { # Type of information detected by the API. # CustomInfoType can either be a new infoType, or an extension of built-in infoType, when the name matches one of existing infoTypes and that infoType is specified in `InspectContent.info_types` field. Specifying the latter adds findings to the one detected by the system. If built-in info type is not specified in `InspectContent.info_types` list then the name is treated as a custom info type.
           &quot;name&quot;: &quot;A String&quot;, # Name of the information type. Either a name of your choosing when creating a CustomInfoType, or one of the names listed at https://cloud.google.com/dlp/docs/infotypes-reference when specifying a built-in type. When sending Cloud DLP results to Data Catalog, infoType names should conform to the pattern `[A-Za-z0-9$-_]{1,64}`.
+          &quot;version&quot;: &quot;A String&quot;, # Optional version name for this InfoType.
         },
         &quot;likelihood&quot;: &quot;A String&quot;, # Likelihood to return for this CustomInfoType. This base value can be altered by a detection rule if the finding meets the criteria specified by the rule. Defaults to `VERY_LIKELY` if not specified.
         &quot;regex&quot;: { # Message defining a custom regular expression. # Regular expression based CustomInfoType.
@@ -174,13 +176,15 @@ <h3>Method Details</h3>
     &quot;infoTypes&quot;: [ # Restricts what info_types to look for. The values must correspond to InfoType values returned by ListInfoTypes or listed at https://cloud.google.com/dlp/docs/infotypes-reference. When no InfoTypes or CustomInfoTypes are specified in a request, the system may automatically choose what detectors to run. By default this may be all types, but may change over time as detectors are updated. If you need precise control and predictability as to what detectors are run you should specify specific InfoTypes listed in the reference, otherwise a default list will be used, which may change over time.
       { # Type of information detected by the API.
         &quot;name&quot;: &quot;A String&quot;, # Name of the information type. Either a name of your choosing when creating a CustomInfoType, or one of the names listed at https://cloud.google.com/dlp/docs/infotypes-reference when specifying a built-in type. When sending Cloud DLP results to Data Catalog, infoType names should conform to the pattern `[A-Za-z0-9$-_]{1,64}`.
+        &quot;version&quot;: &quot;A String&quot;, # Optional version name for this InfoType.
       },
     ],
     &quot;limits&quot;: { # Configuration to control the number of findings returned. Cannot be set if de-identification is requested. # Configuration to control the number of findings returned.
       &quot;maxFindingsPerInfoType&quot;: [ # Configuration of findings limit given for specified infoTypes.
         { # Max findings configuration per infoType, per content item or long running DlpJob.
           &quot;infoType&quot;: { # Type of information detected by the API. # Type of information the findings limit applies to. Only one limit per info_type should be provided. If InfoTypeLimit does not have an info_type, the DLP API applies the limit against all info_types that are found but not specified in another InfoTypeLimit.
             &quot;name&quot;: &quot;A String&quot;, # Name of the information type. Either a name of your choosing when creating a CustomInfoType, or one of the names listed at https://cloud.google.com/dlp/docs/infotypes-reference when specifying a built-in type. When sending Cloud DLP results to Data Catalog, infoType names should conform to the pattern `[A-Za-z0-9$-_]{1,64}`.
+            &quot;version&quot;: &quot;A String&quot;, # Optional version name for this InfoType.
           },
           &quot;maxFindings&quot;: 42, # Max findings limit for the given infoType.
         },
@@ -194,6 +198,7 @@ <h3>Method Details</h3>
         &quot;infoTypes&quot;: [ # List of infoTypes this rule set is applied to.
           { # Type of information detected by the API.
             &quot;name&quot;: &quot;A String&quot;, # Name of the information type. Either a name of your choosing when creating a CustomInfoType, or one of the names listed at https://cloud.google.com/dlp/docs/infotypes-reference when specifying a built-in type. When sending Cloud DLP results to Data Catalog, infoType names should conform to the pattern `[A-Za-z0-9$-_]{1,64}`.
+            &quot;version&quot;: &quot;A String&quot;, # Optional version name for this InfoType.
           },
         ],
         &quot;rules&quot;: [ # Set of rules to be applied to infoTypes. The rules are applied in order.
@@ -213,6 +218,7 @@ <h3>Method Details</h3>
                 &quot;infoTypes&quot;: [ # InfoType list in ExclusionRule rule drops a finding when it overlaps or contained within with a finding of an infoType from this list. For example, for `InspectionRuleSet.info_types` containing &quot;PHONE_NUMBER&quot;` and `exclusion_rule` containing `exclude_info_types.info_types` with &quot;EMAIL_ADDRESS&quot; the phone number findings are dropped if they overlap with EMAIL_ADDRESS finding. That leads to &quot;[email protected]&quot; to generate only a single finding, namely email address.
                   { # Type of information detected by the API.
                     &quot;name&quot;: &quot;A String&quot;, # Name of the information type. Either a name of your choosing when creating a CustomInfoType, or one of the names listed at https://cloud.google.com/dlp/docs/infotypes-reference when specifying a built-in type. When sending Cloud DLP results to Data Catalog, infoType names should conform to the pattern `[A-Za-z0-9$-_]{1,64}`.
+                    &quot;version&quot;: &quot;A String&quot;, # Optional version name for this InfoType.
                   },
                 ],
               },
@@ -265,6 +271,7 @@ <h3>Method Details</h3>
         &quot;findingId&quot;: &quot;A String&quot;, # The unique finding id.
         &quot;infoType&quot;: { # Type of information detected by the API. # The type of content that might have been found. Provided if `excluded_types` is false.
           &quot;name&quot;: &quot;A String&quot;, # Name of the information type. Either a name of your choosing when creating a CustomInfoType, or one of the names listed at https://cloud.google.com/dlp/docs/infotypes-reference when specifying a built-in type. When sending Cloud DLP results to Data Catalog, infoType names should conform to the pattern `[A-Za-z0-9$-_]{1,64}`.
+          &quot;version&quot;: &quot;A String&quot;, # Optional version name for this InfoType.
         },
         &quot;jobCreateTime&quot;: &quot;A String&quot;, # Time the job started that produced this finding.
         &quot;jobName&quot;: &quot;A String&quot;, # The job that stored the finding.