deps: update dependency com.google.cloud:google-cloud-logging to v3.10.6

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.google.cloud:google-cloud-logging	3.10.3 -> 3.10.6

---

Release Notes

googleapis/java-logging

v3.10.6

Dependencies

• use error_prone_annotation via shared deps (#​1049) (0998b9b)

v3.10.5

Bug Fixes

• resource detection for 2nd gen of Cloud Functions works incorrectly (#​1045) (dda1d0a)

v3.10.4

Dependencies

• update dependency com.google.errorprone:error_prone_annotations to v2.15.0 (#​1037) (b2731c7)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Mend Renovate. View repository job log here.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[lqiu96]

Error:  Rule 2: org.apache.maven.plugins.enforcer.RequireUpperBoundDeps failed with message:
Failed while enforcing RequireUpperBoundDeps. The error(s) are [
Require upper bound dependencies error for com.google.errorprone:error_prone_annotations:2.14.0 paths to dependency are:
+-com.google.cloud:google-cloud-logging-logback:0.127.6-alpha-SNAPSHOT
  +-com.google.cloud:google-cloud-logging:3.10.5
    +-com.google.errorprone:error_prone_annotations:2.14.0 (managed) <-- com.google.errorprone:error_prone_annotations:2.15.0
and
+-com.google.cloud:google-cloud-logging-logback:0.127.6-alpha-SNAPSHOT
  +-com.google.guava:guava:31.1-jre
    +-com.google.errorprone:error_prone_annotations:2.14.0 (managed) <-- com.google.errorprone:error_prone_annotations:2.11.0
and
+-com.google.cloud:google-cloud-logging-logback:0.127.6-alpha-SNAPSHOT
  +-com.google.cloud:google-cloud-logging:3.10.5
    +-com.google.api.grpc:proto-google-cloud-logging-v2:0.99.5
      +-com.google.errorprone:error_prone_annotations:2.14.0 (managed) <-- com.google.errorprone:error_prone_annotations:2.14.0
]

From: https://maven.apache.org/enforcer/enforcer-rules/requireUpperBoundDeps.html
Seems that google-cloud-logging is requiring v2.15.0 but the version being pulled in is v2.14.0

[lqiu96]

From the effective pom.xml

      <dependency>
        <groupId>com.google.errorprone</groupId>
        <artifactId>error_prone_annotations</artifactId>
        <version>2.14.0</version>
      </dependency>

google-cloud-logging has version v2.15.0

<dependency>
      <groupId>com.google.errorprone</groupId>
      <artifactId>error_prone_annotations</artifactId>
      <version>2.15.0</version>
      <scope>compile</scope>
      <optional>false</optional>
    </dependency>

Not sure why it's pulling in v2.14.0 (proto-google-cloud-logging) since is 2 leaps away google-cloud-logging -> proto-google-cloud-logging.
Error_prone from Guava seems to be 1 leap away (guava)

It should be pulling in v2.11.0 from guava? Either way it would fail the check since the upper bound is asking for v2.15.0. Could explicitly declare errorprone_annotations as a dependency (version can be set by shared-dependencies)

It is pulling it in due to the import scope of shared-dependencies. It has dependency management section which explicitly sets the version of errorprone to be v2.14.0. We've removed java-logging setting errorpone version explicitly to v2.15.0 and have it pull the version from shared-dependencies to keep the versions in sync.