Regenerate servicemanagement client (googleapis#6926)

This PR was generated using Autosynth. 🌈


<details><summary>Log from Synthtool</summary>

```
2021-01-26 03:55:55,926 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/google-api-java-client-services/synth.py.
On branch autosynth-servicemanagement
nothing to commit, working tree clean
2021-01-26 03:55:56,354 synthtool [DEBUG] > Cloning https://github.com/googleapis/discovery-artifact-manager.git.
DEBUG:synthtool:Cloning https://github.com/googleapis/discovery-artifact-manager.git.
2021-01-26 03:55:56,752 synthtool [DEBUG] > Cleaning output directory.
DEBUG:synthtool:Cleaning output directory.
2021-01-26 03:55:56,754 synthtool [DEBUG] > Installing dependencies.
DEBUG:synthtool:Installing dependencies.
2021-01-26 03:55:58,452 synthtool [INFO] > Generating servicemanagement v1.
INFO:synthtool:Generating servicemanagement v1.
2021-01-26 03:55:58,452 synthtool [INFO] > 	1.31.0
INFO:synthtool:	1.31.0
WARNING:root:object without properties DeleteServiceStrategy: OrderedDict([(u'description', u'Strategy used to delete a service. This strategy is a placeholder only used by the system generated rollout to delete a service.'), (u'id', u'DeleteServiceStrategy'), (u'properties', OrderedDict()), (u'type', u'object')])
WARNING:root:object without properties DisableServiceResponse: OrderedDict([(u'id', u'DisableServiceResponse'), (u'properties', OrderedDict()), (u'type', u'object'), (u'description', u'Operation payload for DisableService method.')])
WARNING:root:object without properties EnableServiceResponse: OrderedDict([(u'properties', OrderedDict()), (u'type', u'object'), (u'id', u'EnableServiceResponse'), (u'description', u'Operation payload for EnableService method.')])
Writing json metadata to clients/google-api-services-servicemanagement/v1.metadata.json
2021-01-26 03:55:59,881 synthtool [DEBUG] > Wrote metadata to clients/google-api-services-servicemanagement/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/google-api-services-servicemanagement/synth.metadata.

```
</details>

Full log will be available here:
https://source.cloud.google.com/results/invocations/1a42608d-cd17-42ae-9390-c3421c65638c/targets

- [ ] To automatically regenerate this PR, check this box.

Author: yoshi-automation

clients/google-api-services-servicemanagement/v1.metadata.json

@@ -2,6 +2,6 @@
   "maven": {
     "groupId": "com.google.apis",
     "artifactId": "google-api-services-servicemanagement",
-    "version": "v1-rev20210108-1.31.0"
+    "version": "v1-rev20210122-1.31.0"
   }
 }

clients/google-api-services-servicemanagement/v1/1.31.0/README.md

@@ -22,7 +22,7 @@ Add the following lines to your `pom.xml` file:
     <dependency>
       <groupId>com.google.apis</groupId>
       <artifactId>google-api-services-servicemanagement</artifactId>
-      <version>v1-rev20210108-1.31.0</version>
+      <version>v1-rev20210122-1.31.0</version>
     </dependency>
   </dependencies>
 </project>
@@ -35,7 +35,7 @@ repositories {
   mavenCentral()
 }
 dependencies {
-  compile 'com.google.apis:google-api-services-servicemanagement:v1-rev20210108-1.31.0'
+  compile 'com.google.apis:google-api-services-servicemanagement:v1-rev20210122-1.31.0'
 }
 ```
 

clients/google-api-services-servicemanagement/v1/1.31.0/com/google/api/services/servicemanagement/model/MetricDescriptor.java

@@ -115,17 +115,17 @@ public final class MetricDescriptor extends com.google.api.client.json.GenericJs
   /**
    * The units in which the metric value is reported. It is only applicable if the `value_type` is
    * `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit` defines the representation of the stored
-   * metric values. Different systems may scale the values to be more easily displayed (so a value
-   * of `0.02KBy` _might_ be displayed as `20By`, and a value of `3523KBy` _might_ be displayed as
-   * `3.5MBy`). However, if the `unit` is `KBy`, then the value of the metric is always in thousands
-   * of bytes, no matter how it may be displayed.. If you want a custom metric to record the exact
+   * metric values. Different systems might scale the values to be more easily displayed (so a value
+   * of `0.02kBy` _might_ be displayed as `20By`, and a value of `3523kBy` _might_ be displayed as
+   * `3.5MBy`). However, if the `unit` is `kBy`, then the value of the metric is always in thousands
+   * of bytes, no matter how it might be displayed. If you want a custom metric to record the exact
    * number of CPU-seconds used by a job, you can create an `INT64 CUMULATIVE` metric whose `unit`
    * is `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005 CPU-seconds, then
    * the value is written as `12005`. Alternatively, if you want a custom metric to record data in a
    * more granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is `ks{CPU}`, and
    * then write the value `12.005` (which is `12005/1000`), or use `Kis{CPU}` and write `11.723`
    * (which is `12005/1024`). The supported units are a subset of [The Unified Code for Units of
-   * Measure](http://unitsofmeasure.org/ucum.html) standard: **Basic units (UNIT)** * `bit` bit *
+   * Measure](https://unitsofmeasure.org/ucum.html) standard: **Basic units (UNIT)** * `bit` bit *
    * `By` byte * `s` second * `min` minute * `h` hour * `d` day * `1` dimensionless **Prefixes
    * (PREFIX)** * `k` kilo (10^3) * `M` mega (10^6) * `G` giga (10^9) * `T` tera (10^12) * `P` peta
    * (10^15) * `E` exa (10^18) * `Z` zetta (10^21) * `Y` yotta (10^24) * `m` milli (10^-3) * `u`
@@ -344,17 +344,17 @@ public MetricDescriptor setType(java.lang.String type) {
   /**
    * The units in which the metric value is reported. It is only applicable if the `value_type` is
    * `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit` defines the representation of the stored
-   * metric values. Different systems may scale the values to be more easily displayed (so a value
-   * of `0.02KBy` _might_ be displayed as `20By`, and a value of `3523KBy` _might_ be displayed as
-   * `3.5MBy`). However, if the `unit` is `KBy`, then the value of the metric is always in thousands
-   * of bytes, no matter how it may be displayed.. If you want a custom metric to record the exact
+   * metric values. Different systems might scale the values to be more easily displayed (so a value
+   * of `0.02kBy` _might_ be displayed as `20By`, and a value of `3523kBy` _might_ be displayed as
+   * `3.5MBy`). However, if the `unit` is `kBy`, then the value of the metric is always in thousands
+   * of bytes, no matter how it might be displayed. If you want a custom metric to record the exact
    * number of CPU-seconds used by a job, you can create an `INT64 CUMULATIVE` metric whose `unit`
    * is `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005 CPU-seconds, then
    * the value is written as `12005`. Alternatively, if you want a custom metric to record data in a
    * more granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is `ks{CPU}`, and
    * then write the value `12.005` (which is `12005/1000`), or use `Kis{CPU}` and write `11.723`
    * (which is `12005/1024`). The supported units are a subset of [The Unified Code for Units of
-   * Measure](http://unitsofmeasure.org/ucum.html) standard: **Basic units (UNIT)** * `bit` bit *
+   * Measure](https://unitsofmeasure.org/ucum.html) standard: **Basic units (UNIT)** * `bit` bit *
    * `By` byte * `s` second * `min` minute * `h` hour * `d` day * `1` dimensionless **Prefixes
    * (PREFIX)** * `k` kilo (10^3) * `M` mega (10^6) * `G` giga (10^9) * `T` tera (10^12) * `P` peta
    * (10^15) * `E` exa (10^18) * `Z` zetta (10^21) * `Y` yotta (10^24) * `m` milli (10^-3) * `u`
@@ -389,17 +389,17 @@ public java.lang.String getUnit() {
   /**
    * The units in which the metric value is reported. It is only applicable if the `value_type` is
    * `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit` defines the representation of the stored
-   * metric values. Different systems may scale the values to be more easily displayed (so a value
-   * of `0.02KBy` _might_ be displayed as `20By`, and a value of `3523KBy` _might_ be displayed as
-   * `3.5MBy`). However, if the `unit` is `KBy`, then the value of the metric is always in thousands
-   * of bytes, no matter how it may be displayed.. If you want a custom metric to record the exact
+   * metric values. Different systems might scale the values to be more easily displayed (so a value
+   * of `0.02kBy` _might_ be displayed as `20By`, and a value of `3523kBy` _might_ be displayed as
+   * `3.5MBy`). However, if the `unit` is `kBy`, then the value of the metric is always in thousands
+   * of bytes, no matter how it might be displayed. If you want a custom metric to record the exact
    * number of CPU-seconds used by a job, you can create an `INT64 CUMULATIVE` metric whose `unit`
    * is `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005 CPU-seconds, then
    * the value is written as `12005`. Alternatively, if you want a custom metric to record data in a
    * more granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is `ks{CPU}`, and
    * then write the value `12.005` (which is `12005/1000`), or use `Kis{CPU}` and write `11.723`
    * (which is `12005/1024`). The supported units are a subset of [The Unified Code for Units of
-   * Measure](http://unitsofmeasure.org/ucum.html) standard: **Basic units (UNIT)** * `bit` bit *
+   * Measure](https://unitsofmeasure.org/ucum.html) standard: **Basic units (UNIT)** * `bit` bit *
    * `By` byte * `s` second * `min` minute * `h` hour * `d` day * `1` dimensionless **Prefixes
    * (PREFIX)** * `k` kilo (10^3) * `M` mega (10^6) * `G` giga (10^9) * `T` tera (10^12) * `P` peta
    * (10^15) * `E` exa (10^18) * `Z` zetta (10^21) * `Y` yotta (10^24) * `m` milli (10^-3) * `u`

clients/google-api-services-servicemanagement/v1/1.31.0/pom.xml

@@ -8,8 +8,8 @@
 
   <groupId>com.google.apis</groupId>
   <artifactId>google-api-services-servicemanagement</artifactId>
-  <version>v1-rev20210108-1.31.0</version>
-  <name>Service Management API v1-rev20210108-1.31.0</name>
+  <version>v1-rev20210122-1.31.0</version>
+  <name>Service Management API v1-rev20210122-1.31.0</name>
   <packaging>jar</packaging>
 
   <inceptionYear>2011</inceptionYear>