fix(safebrowsing): update the API

#### safebrowsing:v5

The following keys were changed:
- schemas.GoogleSecuritySafebrowsingV5SearchHashesResponse.properties.cacheDuration.description

discovery/safebrowsing-v5.json

@@ -121,7 +121,7 @@
       }
     }
   },
-  "revision": "20240505",
+  "revision": "20240428",
   "rootUrl": "https://safebrowsing.googleapis.com/",
   "schemas": {
     "GoogleSecuritySafebrowsingV5FullHash": {
@@ -190,7 +190,7 @@
       "id": "GoogleSecuritySafebrowsingV5SearchHashesResponse",
       "properties": {
         "cacheDuration": {
-          "description": "The client-side cache duration. The client MUST add this duration to the current time to determine the expiration time. The expiration time then applies to every hash prefix queried by the client in the request, regardless of how many full hashes are returned in the response. Even if the server returns no full hashes for a particular hash prefix, this fact MUST also be cached by the client. If and only if the field `full_hashes` is empty, the client MAY increase the `cache_duration` to determine a new expiration that is later than that specified by the server. In any case, the increased cache duration must not be longer than 24 hours. Important: the client MUST NOT assume that the server will return the same cache duration for all responses. The server MAY choose different cache durations for different responses depending on the situation.",
+          "description": "The client-side cache duration. The client MUST add this duration to the current time to determine the expiration time. The expiration time then applies to every hash prefix queried by the client in the request, regardless of how many full hashes are returned in the response. Even if the server returns no full hashes for a particular hash prefix, this fact MUST also be cached by the client. Important: the client MUST NOT assume that the server will return the same cache duration for all responses. The server MAY choose different cache durations for different responses depending on the situation.",
           "format": "google-duration",
           "type": "string"
         },

src/apis/safebrowsing/v5.ts

@@ -155,7 +155,7 @@ export namespace safebrowsing_v5 {
    */
   export interface Schema$GoogleSecuritySafebrowsingV5SearchHashesResponse {
     /**
-     * The client-side cache duration. The client MUST add this duration to the current time to determine the expiration time. The expiration time then applies to every hash prefix queried by the client in the request, regardless of how many full hashes are returned in the response. Even if the server returns no full hashes for a particular hash prefix, this fact MUST also be cached by the client. If and only if the field `full_hashes` is empty, the client MAY increase the `cache_duration` to determine a new expiration that is later than that specified by the server. In any case, the increased cache duration must not be longer than 24 hours. Important: the client MUST NOT assume that the server will return the same cache duration for all responses. The server MAY choose different cache durations for different responses depending on the situation.
+     * The client-side cache duration. The client MUST add this duration to the current time to determine the expiration time. The expiration time then applies to every hash prefix queried by the client in the request, regardless of how many full hashes are returned in the response. Even if the server returns no full hashes for a particular hash prefix, this fact MUST also be cached by the client. Important: the client MUST NOT assume that the server will return the same cache duration for all responses. The server MAY choose different cache durations for different responses depending on the situation.
      */
     cacheDuration?: string | null;
     /**