feat(cloudsearch): update the API

#### cloudsearch:v1

The following keys were added:
- schemas.DynamiteMessagesScoringInfo.properties.lastReadTimestampAgeInDays.format
- schemas.DynamiteMessagesScoringInfo.properties.lastReadTimestampAgeInDays.type

The following keys were changed:
- schemas.Annotation.properties.localId.description
- schemas.Annotation.properties.uniqueId.description
- schemas.CoActivity.properties.coActivityApp.enum
- schemas.CoActivity.properties.coActivityApp.enumDescriptions
- schemas.UploadMetadata.properties.attachmentToken.description

Author: yoshi-automation

discovery/cloudsearch-v1.json

@@ -2077,7 +2077,7 @@
       }
     }
   },
-  "revision": "20230124",
+  "revision": "20230131",
   "rootUrl": "https://cloudsearch.googleapis.com/",
   "schemas": {
     "AbuseReportingConfig": {
@@ -2384,7 +2384,7 @@
           "type": "integer"
         },
         "localId": {
-          "description": "A unique client-assigned ID for this annotation. This is helpful in matching the back-filled annotations to the original annotations on client side, without having to re-parse the message.",
+          "description": "* A client-assigned ID for this annotation. This is helpful in matching the back-filled annotations to the original annotations on client side, without having to re-parse the message. There is no guarantee an annotation has a local_id, it's a purely client used and controlled field with no guarantee of uniqueness.",
           "type": "string"
         },
         "membershipChanged": {
@@ -2480,7 +2480,7 @@
           "type": "string"
         },
         "uniqueId": {
-          "description": "A unique server-assigned ID for this annotation. This is helpful in matching annotation objects when fetched from service.",
+          "description": "* A unique server-assigned ID for this annotation. This is helpful in matching annotation objects when fetched from service. All uploads should have a unique_id after the message they are attached to is successfully sent. Url annotations that originally were uploads (i.e. policy violations) will have a unique_id after the message they are attached to is successfully sent. No other url annotations should have a unique_id. All drive annotations should have a unique_id after the message they are attached to is successfully sent.",
           "type": "string"
         },
         "uploadMetadata": {
@@ -6431,7 +6431,8 @@
             "CO_ACTIVITY_APP_KAHOOT",
             "CO_ACTIVITY_APP_GQUEUES",
             "CO_ACTIVITY_APP_YOU_TUBE_MUSIC",
-            "CO_ACTIVITY_APP_SAMSUNG_NOTES"
+            "CO_ACTIVITY_APP_SAMSUNG_NOTES",
+            "CO_ACTIVITY_APP_HAPPY_AARDVARK"
           ],
           "enumDescriptions": [
             "Should never be used.",
@@ -6442,7 +6443,8 @@
             "Kahoot! educational software.",
             "GQueues task manager.",
             "YouTube Music",
-            "Samsung Notes"
+            "Samsung Notes",
+            "."
           ],
           "type": "string"
         }
@@ -7559,6 +7561,10 @@
           "format": "double",
           "type": "number"
         },
+        "lastReadTimestampAgeInDays": {
+          "format": "double",
+          "type": "number"
+        },
         "messageAgeInDays": {
           "format": "double",
           "type": "number"
@@ -17558,7 +17564,7 @@
       "id": "UploadMetadata",
       "properties": {
         "attachmentToken": {
-          "description": "Opaque token. Clients shall simply pass it back to the Backend. This field will NOT be saved into storage.",
+          "description": "Opaque token. Clients shall simply pass it back to the Backend. There is no guarantee the attachment_token returned on subsequent reads is the same even if nothing has changed. This field will NOT be saved into storage.",
           "type": "string"
         },
         "backendUploadMetadata": {

src/apis/cloudsearch/v1.ts

@@ -268,7 +268,7 @@ export namespace cloudsearch_v1 {
      */
     length?: number | null;
     /**
-     * A unique client-assigned ID for this annotation. This is helpful in matching the back-filled annotations to the original annotations on client side, without having to re-parse the message.
+     * * A client-assigned ID for this annotation. This is helpful in matching the back-filled annotations to the original annotations on client side, without having to re-parse the message. There is no guarantee an annotation has a local_id, it's a purely client used and controlled field with no guarantee of uniqueness.
      */
     localId?: string | null;
     /**
@@ -295,7 +295,7 @@ export namespace cloudsearch_v1 {
      */
     type?: string | null;
     /**
-     * A unique server-assigned ID for this annotation. This is helpful in matching annotation objects when fetched from service.
+     * * A unique server-assigned ID for this annotation. This is helpful in matching annotation objects when fetched from service. All uploads should have a unique_id after the message they are attached to is successfully sent. Url annotations that originally were uploads (i.e. policy violations) will have a unique_id after the message they are attached to is successfully sent. No other url annotations should have a unique_id. All drive annotations should have a unique_id after the message they are attached to is successfully sent.
      */
     uniqueId?: string | null;
     uploadMetadata?: Schema$UploadMetadata;
@@ -3401,6 +3401,7 @@ export namespace cloudsearch_v1 {
     finalScore?: number | null;
     freshnessScore?: number | null;
     joinedSpaceAffinityScore?: number | null;
+    lastReadTimestampAgeInDays?: number | null;
     messageAgeInDays?: number | null;
     messageSenderAffinityScore?: number | null;
     spaceId?: string | null;
@@ -8348,7 +8349,7 @@ export namespace cloudsearch_v1 {
    */
   export interface Schema$UploadMetadata {
     /**
-     * Opaque token. Clients shall simply pass it back to the Backend. This field will NOT be saved into storage.
+     * Opaque token. Clients shall simply pass it back to the Backend. There is no guarantee the attachment_token returned on subsequent reads is the same even if nothing has changed. This field will NOT be saved into storage.
      */
     attachmentToken?: string | null;
     /**