feat(workloadmanager): update the api

#### workloadmanager:v1

The following keys were deleted:
- schemas.APILayerServer (Total Keys: 9)
- schemas.AvailabilityGroup (Total Keys: 12)
- schemas.BackendServer (Total Keys: 13)
- schemas.Cluster (Total Keys: 7)
- schemas.Database (Total Keys: 10)
- schemas.FrontEndServer (Total Keys: 9)
- schemas.LoadBalancerServer (Total Keys: 6)
- schemas.SqlserverWorkload (Total Keys: 12)
- schemas.ThreeTierWorkload (Total Keys: 10)
- schemas.WorkloadProfile.properties.sqlserverWorkload.$ref (Total Keys: 1)
- schemas.WorkloadProfile.properties.threeTierWorkload.$ref (Total Keys: 1)

The following keys were added:
- schemas.UpcomingMaintenanceEvent.properties.onHostMaintenance.type (Total Keys: 1)

Author: yoshi-automation

docs/dyn/workloadmanager_v1.projects.locations.discoveredprofiles.healthes.html

@@ -126,6 +126,7 @@ <h3>Method Details</h3>
               &quot;upcomingMaintenanceEvent&quot;: { # Maintenance Event # Optional. the next maintenance event on VM
                 &quot;endTime&quot;: &quot;A String&quot;, # Optional. End time
                 &quot;maintenanceStatus&quot;: &quot;A String&quot;, # Optional. Maintenance status
+                &quot;onHostMaintenance&quot;: &quot;A String&quot;, # Optional. Instance maintenance behavior. Could be &quot;MIGRATE&quot; or &quot;TERMINATE&quot;.
                 &quot;startTime&quot;: &quot;A String&quot;, # Optional. Start time
                 &quot;type&quot;: &quot;A String&quot;, # Optional. Type
               },