feat(ondemandscanning): update the api

#### ondemandscanning:v1

The following keys were added:
- schemas.Binary (Total Keys: 4)
- schemas.PackageData.properties.binary.$ref (Total Keys: 1)

#### ondemandscanning:v1beta1

The following keys were added:
- schemas.Binary (Total Keys: 4)
- schemas.PackageData.properties.binary.$ref (Total Keys: 1)

Author: yoshi-automation

docs/dyn/ondemandscanning_v1.projects.locations.scans.html

@@ -100,6 +100,10 @@ <h3>Method Details</h3>
   &quot;packages&quot;: [ # The packages to analyze.
     {
       &quot;architecture&quot;: &quot;A String&quot;, # The architecture of the package.
+      &quot;binary&quot;: { # The binary package. This is significant when the source is different than the binary itself. Historically if they&#x27;ve differed, we&#x27;ve stored the name of the source and its version in the package/version fields, but we should also store the binary package info, as that&#x27;s what&#x27;s actually installed. See https://b.corp.google.com/issues/175908657#comment15
+        &quot;name&quot;: &quot;A String&quot;,
+        &quot;version&quot;: &quot;A String&quot;,
+      },
       &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) in which the vulnerability may manifest. Examples include distro or storage location for vulnerable jar.
       &quot;dependencyChain&quot;: [ # The dependency chain between this package and the user&#x27;s artifact. List in order from the customer&#x27;s package under review first, to the current package last. Inclusive of the original package and the current package.
         { # Indicates a language package available between this package and the customer&#x27;s resource artifact.

docs/dyn/ondemandscanning_v1beta1.projects.locations.scans.html

@@ -99,6 +99,10 @@ <h3>Method Details</h3>
   &quot;packages&quot;: [ # The packages to analyze.
     {
       &quot;architecture&quot;: &quot;A String&quot;, # The architecture of the package.
+      &quot;binary&quot;: { # The binary package. This is significant when the source is different than the binary itself. Historically if they&#x27;ve differed, we&#x27;ve stored the name of the source and its version in the package/version fields, but we should also store the binary package info, as that&#x27;s what&#x27;s actually installed. See https://b.corp.google.com/issues/175908657#comment15
+        &quot;name&quot;: &quot;A String&quot;,
+        &quot;version&quot;: &quot;A String&quot;,
+      },
       &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) in which the vulnerability may manifest. Examples include distro or storage location for vulnerable jar.
       &quot;dependencyChain&quot;: [ # The dependency chain between this package and the user&#x27;s artifact. List in order from the customer&#x27;s package under review first, to the current package last. Inclusive of the original package and the current package.
         { # Indicates a language package available between this package and the customer&#x27;s resource artifact.

googleapiclient/discovery_cache/documents/ondemandscanning.v1.json

@@ -339,7 +339,7 @@
       }
     }
   },
-  "revision": "20230320",
+  "revision": "20230327",
   "rootUrl": "https://ondemandscanning.googleapis.com/",
   "schemas": {
     "AliasContext": {
@@ -506,6 +506,18 @@
       },
       "type": "object"
     },
+    "Binary": {
+      "id": "Binary",
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "version": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "BuildOccurrence": {
       "description": "Details of a build occurrence.",
       "id": "BuildOccurrence",
@@ -1730,6 +1742,10 @@
           "description": "The architecture of the package.",
           "type": "string"
         },
+        "binary": {
+          "$ref": "Binary",
+          "description": "The binary package. This is significant when the source is different than the binary itself. Historically if they've differed, we've stored the name of the source and its version in the package/version fields, but we should also store the binary package info, as that's what's actually installed. See https://b.corp.google.com/issues/175908657#comment15"
+        },
         "cpeUri": {
           "description": "The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) in which the vulnerability may manifest. Examples include distro or storage location for vulnerable jar.",
           "type": "string"

googleapiclient/discovery_cache/documents/ondemandscanning.v1beta1.json

@@ -339,7 +339,7 @@
       }
     }
   },
-  "revision": "20230320",
+  "revision": "20230327",
   "rootUrl": "https://ondemandscanning.googleapis.com/",
   "schemas": {
     "AliasContext": {
@@ -502,6 +502,18 @@
       },
       "type": "object"
     },
+    "Binary": {
+      "id": "Binary",
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "version": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "BuildOccurrence": {
       "description": "Details of a build occurrence.",
       "id": "BuildOccurrence",
@@ -1726,6 +1738,10 @@
           "description": "The architecture of the package.",
           "type": "string"
         },
+        "binary": {
+          "$ref": "Binary",
+          "description": "The binary package. This is significant when the source is different than the binary itself. Historically if they've differed, we've stored the name of the source and its version in the package/version fields, but we should also store the binary package info, as that's what's actually installed. See https://b.corp.google.com/issues/175908657#comment15"
+        },
         "cpeUri": {
           "description": "The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) in which the vulnerability may manifest. Examples include distro or storage location for vulnerable jar.",
           "type": "string"