feat(cloudsearch): update the api

#### cloudsearch:v1

The following keys were added:
- schemas.Annotation.properties.inlineRenderFormat.type (Total Keys: 1)
- schemas.Annotation.properties.interactionData.$ref (Total Keys: 1)
- schemas.InteractionData (Total Keys: 2)
- schemas.MessageInfo.properties.authorUserType.type (Total Keys: 1)

Author: yoshi-automation

googleapiclient/discovery_cache/documents/cloudsearch.v1.json

@@ -2077,7 +2077,7 @@
       }
     }
   },
-  "revision": "20230214",
+  "revision": "20230221",
   "rootUrl": "https://cloudsearch.googleapis.com/",
   "schemas": {
     "AbuseReportingConfig": {
@@ -2322,7 +2322,7 @@
       "type": "object"
     },
     "Annotation": {
-      "description": "NOTE WHEN ADDING NEW PROTO FIELDS: Be sure to add datapol annotations to new fields with potential PII, so they get scrubbed when logging protos for errors. NEXT TAG: 29",
+      "description": "NOTE WHEN ADDING NEW PROTO FIELDS: Be sure to add datapol annotations to new fields with potential PII, so they get scrubbed when logging protos for errors. NEXT TAG: 31",
       "id": "Annotation",
       "properties": {
         "babelPlaceholderMetadata": {
@@ -2333,7 +2333,7 @@
           "description": "LINT.ThenChange(//depot/google3/java/com/google/apps/dynamite/v1/backend/action/common/SystemMessageHelper.java)"
         },
         "chipRenderType": {
-          "description": "Whether the annotation should be rendered as a chip. If this is missing or unspecified, fallback to should_not_render on the metadata.",
+          "description": "Whether the annotation should be rendered as a preview chip. If this is missing or unspecified, fallback to should_not_render on the metadata.",
           "enum": [
             "CHIP_RENDER_TYPE_UNSPECIFIED",
             "RENDER",
@@ -2342,9 +2342,9 @@
           ],
           "enumDescriptions": [
             "",
-            "Clients must render the annotation as a chip, and if they cannot render this many Annotations, show a fallback card.",
+            "Clients must render the annotation as a preview chip, and if they cannot render this many Annotations, show a fallback card.",
             "Client can render the annotation if it has room to render it.",
-            "Client should not render the annotation as a chip."
+            "Client should not render the annotation as a preview chip."
           ],
           "type": "string"
         },
@@ -2374,10 +2374,26 @@
         "incomingWebhookChangedMetadata": {
           "$ref": "IncomingWebhookChangedMetadata"
         },
+        "inlineRenderFormat": {
+          "description": "The inline render format of this annotation. go/drive-smart-chips-chat-v2.",
+          "enum": [
+            "INLINE_RENDER_FORMAT_UNSPECIFIED",
+            "SMART_CHIP"
+          ],
+          "enumDescriptions": [
+            "",
+            ""
+          ],
+          "type": "string"
+        },
         "integrationConfigUpdated": {
           "$ref": "IntegrationConfigUpdatedMetadata",
           "description": "LINT.ThenChange(//depot/google3/java/com/google/apps/dynamite/v1/backend/action/common/SystemMessageHelper.java)"
         },
+        "interactionData": {
+          "$ref": "InteractionData",
+          "description": "Additional interaction data for this annotation."
+        },
         "length": {
           "description": "Length of the text_body substring beginning from start_index the Annotation corresponds to.",
           "format": "int32",
@@ -11479,6 +11495,17 @@
       },
       "type": "object"
     },
+    "InteractionData": {
+      "description": "Interaction data for an annotation, which may be supplemental to the metadata oneof. For example, this will contain the fully built navigation target for smart chips. NEXT TAG: 2",
+      "id": "InteractionData",
+      "properties": {
+        "url": {
+          "$ref": "SafeUrlProto",
+          "description": "A general navigation target associated with the annotation this message is contained in. For smart chips, this will be the destination of the tap/click target and will be returned by the server. For scenarios where the chip originated from a user-provided url, this value will be provided by clients; otherwise it will be built by the corresponding metadata parts."
+        }
+      },
+      "type": "object"
+    },
     "InviteAcceptedEvent": {
       "id": "InviteAcceptedEvent",
       "properties": {
@@ -13111,6 +13138,18 @@
     "MessageInfo": {
       "id": "MessageInfo",
       "properties": {
+        "authorUserType": {
+          "description": "Message author\u2019s user type (human/bot).",
+          "enum": [
+            "HUMAN",
+            "BOT"
+          ],
+          "enumDescriptions": [
+            "Notes on HUMAN type: 1) Leaving UserId.UserType field empty will return HUMAN as default value. This is expected because all the existing UserIds are without explicitly setting UserType, most of which are HUMAN Ids. For Bot Ids we will always set BOT in UserType field. 2) DO NOT explicitly set HUMAN as type. This is a proto2 issue, that a UserId with explicitly set default value HUMAN as type is NOT equal to an id without setting the field. aka. UserId id1 = UserId.newBuilder() .setId(\"dummy\").setType(UserType.HUMAN).build(); UserId id2 = UserId.newBuilder().setId(\"dummy\").build(); AssertThat(id1).isNotEqual(id2); AssertThat(id2.getType()).isEqualTo(UserType.HUMAN);",
+            ""
+          ],
+          "type": "string"
+        },
         "message": {
           "$ref": "Message",
           "description": "The content of a matching message."