feat(monitoring): update the api

#### monitoring:v3

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

docs/dyn/monitoring_v3.projects.uptimeCheckConfigs.html

@@ -136,6 +136,7 @@ <h3>Method Details</h3>
     },
     &quot;body&quot;: &quot;A String&quot;, # The request body associated with the HTTP POST request. If content_type is URL_ENCODED, the body passed in must be URL-encoded. Users can provide a Content-Length header via the headers field or the API will do so. If the request_method is GET and body is not empty, the API will return an error. The maximum byte size is 1 megabyte.Note: If client libraries aren&#x27;t used (which performs the conversion automatically) base64 encode your body data since the field is of bytes type.
     &quot;contentType&quot;: &quot;A String&quot;, # The content type header to use for the check. The following configurations result in errors: 1. Content type is specified in both the headers field and the content_type field. 2. Request method is GET and content_type is not TYPE_UNSPECIFIED 3. Request method is POST and content_type is TYPE_UNSPECIFIED. 4. Request method is POST and a &quot;Content-Type&quot; header is provided via headers field. The content_type field should be used instead.
+    &quot;customContentType&quot;: &quot;A String&quot;, # A user provided content type header to use for the check. The invalid configurations outlined in the content_type field apply to custom_content_type, as well as the following: 1. content_type is URL_ENCODED and custom_content_type is set. 2. content_type is USER_PROVIDED and custom_content_type is not set.
     &quot;headers&quot;: { # The list of headers to send as part of the Uptime check request. If two headers have the same key and different values, they should be entered as a single header, with the value being a comma-separated list of all the desired values as described at https://www.w3.org/Protocols/rfc2616/rfc2616.txt (page 31). Entering two separate headers with the same key in a Create call will cause the first to be overwritten by the second. The maximum number of headers allowed is 100.
       &quot;a_key&quot;: &quot;A String&quot;,
     },
@@ -221,6 +222,7 @@ <h3>Method Details</h3>
     },
     &quot;body&quot;: &quot;A String&quot;, # The request body associated with the HTTP POST request. If content_type is URL_ENCODED, the body passed in must be URL-encoded. Users can provide a Content-Length header via the headers field or the API will do so. If the request_method is GET and body is not empty, the API will return an error. The maximum byte size is 1 megabyte.Note: If client libraries aren&#x27;t used (which performs the conversion automatically) base64 encode your body data since the field is of bytes type.
     &quot;contentType&quot;: &quot;A String&quot;, # The content type header to use for the check. The following configurations result in errors: 1. Content type is specified in both the headers field and the content_type field. 2. Request method is GET and content_type is not TYPE_UNSPECIFIED 3. Request method is POST and content_type is TYPE_UNSPECIFIED. 4. Request method is POST and a &quot;Content-Type&quot; header is provided via headers field. The content_type field should be used instead.
+    &quot;customContentType&quot;: &quot;A String&quot;, # A user provided content type header to use for the check. The invalid configurations outlined in the content_type field apply to custom_content_type, as well as the following: 1. content_type is URL_ENCODED and custom_content_type is set. 2. content_type is USER_PROVIDED and custom_content_type is not set.
     &quot;headers&quot;: { # The list of headers to send as part of the Uptime check request. If two headers have the same key and different values, they should be entered as a single header, with the value being a comma-separated list of all the desired values as described at https://www.w3.org/Protocols/rfc2616/rfc2616.txt (page 31). Entering two separate headers with the same key in a Create call will cause the first to be overwritten by the second. The maximum number of headers allowed is 100.
       &quot;a_key&quot;: &quot;A String&quot;,
     },
@@ -331,6 +333,7 @@ <h3>Method Details</h3>
     },
     &quot;body&quot;: &quot;A String&quot;, # The request body associated with the HTTP POST request. If content_type is URL_ENCODED, the body passed in must be URL-encoded. Users can provide a Content-Length header via the headers field or the API will do so. If the request_method is GET and body is not empty, the API will return an error. The maximum byte size is 1 megabyte.Note: If client libraries aren&#x27;t used (which performs the conversion automatically) base64 encode your body data since the field is of bytes type.
     &quot;contentType&quot;: &quot;A String&quot;, # The content type header to use for the check. The following configurations result in errors: 1. Content type is specified in both the headers field and the content_type field. 2. Request method is GET and content_type is not TYPE_UNSPECIFIED 3. Request method is POST and content_type is TYPE_UNSPECIFIED. 4. Request method is POST and a &quot;Content-Type&quot; header is provided via headers field. The content_type field should be used instead.
+    &quot;customContentType&quot;: &quot;A String&quot;, # A user provided content type header to use for the check. The invalid configurations outlined in the content_type field apply to custom_content_type, as well as the following: 1. content_type is URL_ENCODED and custom_content_type is set. 2. content_type is USER_PROVIDED and custom_content_type is not set.
     &quot;headers&quot;: { # The list of headers to send as part of the Uptime check request. If two headers have the same key and different values, they should be entered as a single header, with the value being a comma-separated list of all the desired values as described at https://www.w3.org/Protocols/rfc2616/rfc2616.txt (page 31). Entering two separate headers with the same key in a Create call will cause the first to be overwritten by the second. The maximum number of headers allowed is 100.
       &quot;a_key&quot;: &quot;A String&quot;,
     },
@@ -430,6 +433,7 @@ <h3>Method Details</h3>
         },
         &quot;body&quot;: &quot;A String&quot;, # The request body associated with the HTTP POST request. If content_type is URL_ENCODED, the body passed in must be URL-encoded. Users can provide a Content-Length header via the headers field or the API will do so. If the request_method is GET and body is not empty, the API will return an error. The maximum byte size is 1 megabyte.Note: If client libraries aren&#x27;t used (which performs the conversion automatically) base64 encode your body data since the field is of bytes type.
         &quot;contentType&quot;: &quot;A String&quot;, # The content type header to use for the check. The following configurations result in errors: 1. Content type is specified in both the headers field and the content_type field. 2. Request method is GET and content_type is not TYPE_UNSPECIFIED 3. Request method is POST and content_type is TYPE_UNSPECIFIED. 4. Request method is POST and a &quot;Content-Type&quot; header is provided via headers field. The content_type field should be used instead.
+        &quot;customContentType&quot;: &quot;A String&quot;, # A user provided content type header to use for the check. The invalid configurations outlined in the content_type field apply to custom_content_type, as well as the following: 1. content_type is URL_ENCODED and custom_content_type is set. 2. content_type is USER_PROVIDED and custom_content_type is not set.
         &quot;headers&quot;: { # The list of headers to send as part of the Uptime check request. If two headers have the same key and different values, they should be entered as a single header, with the value being a comma-separated list of all the desired values as described at https://www.w3.org/Protocols/rfc2616/rfc2616.txt (page 31). Entering two separate headers with the same key in a Create call will cause the first to be overwritten by the second. The maximum number of headers allowed is 100.
           &quot;a_key&quot;: &quot;A String&quot;,
         },
@@ -533,6 +537,7 @@ <h3>Method Details</h3>
     },
     &quot;body&quot;: &quot;A String&quot;, # The request body associated with the HTTP POST request. If content_type is URL_ENCODED, the body passed in must be URL-encoded. Users can provide a Content-Length header via the headers field or the API will do so. If the request_method is GET and body is not empty, the API will return an error. The maximum byte size is 1 megabyte.Note: If client libraries aren&#x27;t used (which performs the conversion automatically) base64 encode your body data since the field is of bytes type.
     &quot;contentType&quot;: &quot;A String&quot;, # The content type header to use for the check. The following configurations result in errors: 1. Content type is specified in both the headers field and the content_type field. 2. Request method is GET and content_type is not TYPE_UNSPECIFIED 3. Request method is POST and content_type is TYPE_UNSPECIFIED. 4. Request method is POST and a &quot;Content-Type&quot; header is provided via headers field. The content_type field should be used instead.
+    &quot;customContentType&quot;: &quot;A String&quot;, # A user provided content type header to use for the check. The invalid configurations outlined in the content_type field apply to custom_content_type, as well as the following: 1. content_type is URL_ENCODED and custom_content_type is set. 2. content_type is USER_PROVIDED and custom_content_type is not set.
     &quot;headers&quot;: { # The list of headers to send as part of the Uptime check request. If two headers have the same key and different values, they should be entered as a single header, with the value being a comma-separated list of all the desired values as described at https://www.w3.org/Protocols/rfc2616/rfc2616.txt (page 31). Entering two separate headers with the same key in a Create call will cause the first to be overwritten by the second. The maximum number of headers allowed is 100.
       &quot;a_key&quot;: &quot;A String&quot;,
     },
@@ -619,6 +624,7 @@ <h3>Method Details</h3>
     },
     &quot;body&quot;: &quot;A String&quot;, # The request body associated with the HTTP POST request. If content_type is URL_ENCODED, the body passed in must be URL-encoded. Users can provide a Content-Length header via the headers field or the API will do so. If the request_method is GET and body is not empty, the API will return an error. The maximum byte size is 1 megabyte.Note: If client libraries aren&#x27;t used (which performs the conversion automatically) base64 encode your body data since the field is of bytes type.
     &quot;contentType&quot;: &quot;A String&quot;, # The content type header to use for the check. The following configurations result in errors: 1. Content type is specified in both the headers field and the content_type field. 2. Request method is GET and content_type is not TYPE_UNSPECIFIED 3. Request method is POST and content_type is TYPE_UNSPECIFIED. 4. Request method is POST and a &quot;Content-Type&quot; header is provided via headers field. The content_type field should be used instead.
+    &quot;customContentType&quot;: &quot;A String&quot;, # A user provided content type header to use for the check. The invalid configurations outlined in the content_type field apply to custom_content_type, as well as the following: 1. content_type is URL_ENCODED and custom_content_type is set. 2. content_type is USER_PROVIDED and custom_content_type is not set.
     &quot;headers&quot;: { # The list of headers to send as part of the Uptime check request. If two headers have the same key and different values, they should be entered as a single header, with the value being a comma-separated list of all the desired values as described at https://www.w3.org/Protocols/rfc2616/rfc2616.txt (page 31). Entering two separate headers with the same key in a Create call will cause the first to be overwritten by the second. The maximum number of headers allowed is 100.
       &quot;a_key&quot;: &quot;A String&quot;,
     },

googleapiclient/discovery_cache/documents/monitoring.v1.json

@@ -806,7 +806,7 @@
       }
     }
   },
-  "revision": "20230206",
+  "revision": "20230212",
   "rootUrl": "https://monitoring.googleapis.com/",
   "schemas": {
     "Aggregation": {

googleapiclient/discovery_cache/documents/monitoring.v3.json

@@ -2714,7 +2714,7 @@
       }
     }
   },
-  "revision": "20230206",
+  "revision": "20230212",
   "rootUrl": "https://monitoring.googleapis.com/",
   "schemas": {
     "Aggregation": {
@@ -3823,14 +3823,20 @@
           "description": "The content type header to use for the check. The following configurations result in errors: 1. Content type is specified in both the headers field and the content_type field. 2. Request method is GET and content_type is not TYPE_UNSPECIFIED 3. Request method is POST and content_type is TYPE_UNSPECIFIED. 4. Request method is POST and a \"Content-Type\" header is provided via headers field. The content_type field should be used instead.",
           "enum": [
             "TYPE_UNSPECIFIED",
-            "URL_ENCODED"
+            "URL_ENCODED",
+            "USER_PROVIDED"
           ],
           "enumDescriptions": [
             "No content type specified.",
-            "body is in URL-encoded form. Equivalent to setting the Content-Type to application/x-www-form-urlencoded in the HTTP request."
+            "body is in URL-encoded form. Equivalent to setting the Content-Type to application/x-www-form-urlencoded in the HTTP request.",
+            "body is in custom_content_type form. Equivalent to setting the Content-Type to the contents of custom_content_type in the HTTP request."
           ],
           "type": "string"
         },
+        "customContentType": {
+          "description": "A user provided content type header to use for the check. The invalid configurations outlined in the content_type field apply to custom_content_type, as well as the following: 1. content_type is URL_ENCODED and custom_content_type is set. 2. content_type is USER_PROVIDED and custom_content_type is not set.",
+          "type": "string"
+        },
         "headers": {
           "additionalProperties": {
             "type": "string"