feat(containeranalysis): update the api

#### containeranalysis:v1alpha1

The following keys were added:
- schemas.PackageIssue.properties.effectiveSeverity (Total Keys: 2)
- schemas.PackageIssue.properties.packageType.type (Total Keys: 1)

Author: yoshi-automation

docs/dyn/containeranalysis_v1alpha1.projects.notes.occurrences.html

@@ -517,7 +517,7 @@ <h3>Method Details</h3>
       },
       &quot;vulnerabilityDetails&quot;: { # Used by Occurrence to point to where the vulnerability exists and how to fix it. # Details of a security vulnerability note.
         &quot;cvssScore&quot;: 3.14, # Output only. The CVSS score of this vulnerability. CVSS score is on a scale of 0-10 where 0 indicates low severity and 10 indicates high severity.
-        &quot;effectiveSeverity&quot;: &quot;A String&quot;, # The distro assigned severity for this vulnerability when that is available and note provider assigned severity when distro has not yet assigned a severity for this vulnerability.
+        &quot;effectiveSeverity&quot;: &quot;A String&quot;, # The distro assigned severity for this vulnerability when that is available and note provider assigned severity when distro has not yet assigned a severity for this vulnerability. When there are multiple package issues for this vulnerability, they can have different effective severities because some might come from the distro and some might come from installed language packs (e.g. Maven JARs or Go binaries). For this reason, it is advised to use the effective severity on the PackageIssue level, as this field may eventually be deprecated. In the case where multiple PackageIssues have different effective severities, the one set here will be the highest severity of any of the PackageIssues.
         &quot;packageIssue&quot;: [ # The set of affected locations and their fixes (if available) within the associated resource.
           { # This message wraps a location affected by a vulnerability and its associated fix (if one is available).
             &quot;affectedLocation&quot;: { # The location of the vulnerability # The location of the vulnerability.
@@ -531,6 +531,7 @@ <h3>Method Details</h3>
                 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
               },
             },
+            &quot;effectiveSeverity&quot;: &quot;A String&quot;, # Output only. The distro or language system assigned severity for this vulnerability when that is available and note provider assigned severity when distro or language system has not yet assigned a severity for this vulnerability.
             &quot;fixedLocation&quot;: { # The location of the vulnerability # The location of the available fix for vulnerability.
               &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) format. Examples include distro or storage location for vulnerable jar. This field can be used as a filter in list requests.
               &quot;package&quot;: &quot;A String&quot;, # The package being described.
@@ -542,11 +543,12 @@ <h3>Method Details</h3>
                 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
               },
             },
+            &quot;packageType&quot;: &quot;A String&quot;, # The type of package (e.g. OS, MAVEN, GO).
             &quot;severityName&quot;: &quot;A String&quot;,
           },
         ],
         &quot;severity&quot;: &quot;A String&quot;, # Output only. The note provider assigned Severity of the vulnerability.
-        &quot;type&quot;: &quot;A String&quot;, # The type of package; whether native or non native(ruby gems, node.js packages etc)
+        &quot;type&quot;: &quot;A String&quot;, # The type of package; whether native or non native(ruby gems, node.js packages etc). This may be deprecated in the future because we can have multiple PackageIssues with different package types.
       },
     },
   ],