chore(containeranalysis): update the api

#### containeranalysis:v1alpha1

The following keys were added:
- schemas.Detail.properties.source (Total Keys: 1)
- schemas.Version.properties.inclusive (Total Keys: 1)

#### containeranalysis:v1beta1

The following keys were added:
- schemas.Detail.properties.source (Total Keys: 1)
- schemas.Version.properties.inclusive (Total Keys: 1)

Author: yoshi-automation

docs/dyn/containeranalysis_v1alpha1.projects.notes.html

@@ -324,6 +324,7 @@ <h3>Method Details</h3>
             &quot;path&quot;: &quot;A String&quot;, # The path from which we gathered that this package/version is installed.
             &quot;version&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The version installed at this location.
               &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
+              &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
               &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
               &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
               &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
@@ -358,6 +359,7 @@ <h3>Method Details</h3>
         &quot;package&quot;: &quot;A String&quot;, # Required - The package this Upgrade is for.
         &quot;parsedVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # Required - The version of the package in a machine + human readable form.
           &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
+          &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
           &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
           &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
           &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
@@ -373,6 +375,7 @@ <h3>Method Details</h3>
               &quot;package&quot;: &quot;A String&quot;, # The package being described.
               &quot;version&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The version of the package being described. This field can be used as a filter in list requests.
                 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
+                &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
                 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
                 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
                 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
@@ -383,6 +386,7 @@ <h3>Method Details</h3>
               &quot;package&quot;: &quot;A String&quot;, # The package being described.
               &quot;version&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The version of the package being described. This field can be used as a filter in list requests.
                 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
+                &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
                 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
                 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
                 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.