chore: regenerate people client (googleapis#27125)

Generated in GitHub action: https://togithub.com/googleapis/googleapis/google-api-java-client-services/actions/workflows/codegen.yaml

Author: yoshi-code-bot

clients/google-api-services-people/v1/2.0.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-people</artifactId>
-      <version>v1-rev20240313-2.0.0</version>
+      <version>v1-rev20250513-2.0.0</version>
     </dependency>
   </dependencies>
 </project>
@@ -35,7 +35,7 @@ repositories {
   mavenCentral()
 }
 dependencies {
-  implementation 'com.google.apis:google-api-services-people:v1-rev20240313-2.0.0'
+  implementation 'com.google.apis:google-api-services-people:v1-rev20250513-2.0.0'
 }
 ```
 

clients/google-api-services-people/v1/2.0.0/com/google/api/services/people/v1/PeopleService.java

@@ -4006,11 +4006,13 @@ public SearchDirectoryPeople set(String parameterName, Object value) {
      * not specified for the contact to be updated or if there is no contact source. The server returns
      * a 400 error with reason `"failedPrecondition"` if `person.metadata.sources.etag` is different
      * than the contact's etag, which indicates the contact has changed since its data was read. Clients
-     * should get the latest person and merge their updates into the latest person. The server returns a
-     * 400 error if `memberships` are being updated and there are no contact group memberships specified
-     * on the person. The server returns a 400 error if more than one field is specified on a field that
-     * is a singleton for contact sources: * biographies * birthdays * genders * names Mutate requests
-     * for the same user should be sent sequentially to avoid increased latency and failures.
+     * should get the latest person and merge their updates into the latest person. If making sequential
+     * updates to the same person, the etag from the `updateContact` response should be used to avoid
+     * failures. The server returns a 400 error if `memberships` are being updated and there are no
+     * contact group memberships specified on the person. The server returns a 400 error if more than
+     * one field is specified on a field that is a singleton for contact sources: * biographies *
+     * birthdays * genders * names Mutate requests for the same user should be sent sequentially to
+     * avoid increased latency and failures.
      *
      * Create a request for the method "people.updateContact".
      *
@@ -4042,12 +4044,13 @@ public class UpdateContact extends PeopleServiceRequest<com.google.api.services.
        * not specified for the contact to be updated or if there is no contact source. The server
        * returns a 400 error with reason `"failedPrecondition"` if `person.metadata.sources.etag` is
        * different than the contact's etag, which indicates the contact has changed since its data was
-       * read. Clients should get the latest person and merge their updates into the latest person. The
-       * server returns a 400 error if `memberships` are being updated and there are no contact group
-       * memberships specified on the person. The server returns a 400 error if more than one field is
-       * specified on a field that is a singleton for contact sources: * biographies * birthdays *
-       * genders * names Mutate requests for the same user should be sent sequentially to avoid
-       * increased latency and failures.
+       * read. Clients should get the latest person and merge their updates into the latest person. If
+       * making sequential updates to the same person, the etag from the `updateContact` response should
+       * be used to avoid failures. The server returns a 400 error if `memberships` are being updated
+       * and there are no contact group memberships specified on the person. The server returns a 400
+       * error if more than one field is specified on a field that is a singleton for contact sources: *
+       * biographies * birthdays * genders * names Mutate requests for the same user should be sent
+       * sequentially to avoid increased latency and failures.
        *
        * Create a request for the method "people.updateContact".
        *

clients/google-api-services-people/v1/2.0.0/pom.xml

@@ -8,8 +8,8 @@
 
   <groupId>com.google.apis</groupId>
   <artifactId>google-api-services-people</artifactId>
-  <version>v1-rev20240313-2.0.0</version>
-  <name>People API v1-rev20240313-2.0.0</name>
+  <version>v1-rev20250513-2.0.0</version>
+  <name>People API v1-rev20250513-2.0.0</name>
   <packaging>jar</packaging>
 
   <inceptionYear>2011</inceptionYear>

clients/google-api-services-people/v1/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-people</artifactId>
-      <version>v1-rev20240313-2.0.0</version>
+      <version>v1-rev20250513-2.0.0</version>
     </dependency>
   </dependencies>
 </project>
@@ -35,7 +35,7 @@ repositories {
   mavenCentral()
 }
 dependencies {
-  implementation 'com.google.apis:google-api-services-people:v1-rev20240313-2.0.0'
+  implementation 'com.google.apis:google-api-services-people:v1-rev20250513-2.0.0'
 }
 ```