[java] Update dependency net.bytebuddy:byte-buddy to v1.15.11

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
net.bytebuddy:byte-buddy	1.15.10 -> 1.15.11

---

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, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[qodo-merge-pro]

CI Failure Feedback 🧐

(Checks updated until commit e02ad79)

Action: Check format / Check format script run

Failed stage: Run Bazel [❌]

Failed test name: //scripts:google-java-format

Failure summary: The action failed because the Maven dependencies in the project need to be re-pinned. Specifically: The maven_install.json file contains an invalid input signature This typically occurs when Maven artifacts have been changed but not repinned The build failed while trying to fetch the google-java-format dependency To fix this, the Maven dependencies need to be regenerated by running: REPIN=1 bazel run @maven//:pin

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 961: Package 'php-symfony-debug-bundle' is not installed, so not removed 962: Package 'php-symfony-dependency-injection' is not installed, so not removed 963: Package 'php-symfony-deprecation-contracts' is not installed, so not removed 964: Package 'php-symfony-discord-notifier' is not installed, so not removed 965: Package 'php-symfony-doctrine-bridge' is not installed, so not removed 966: Package 'php-symfony-doctrine-messenger' is not installed, so not removed 967: Package 'php-symfony-dom-crawler' is not installed, so not removed 968: Package 'php-symfony-dotenv' is not installed, so not removed 969: Package 'php-symfony-error-handler' is not installed, so not removed ... 1832: �[32mAnalyzing:�[0m target //scripts:google-java-format (188 packages loaded, 1549 targets configured) 1833: �[32m[1 / 1]�[0m checking cached actions 1834: �[32mAnalyzing:�[0m target //scripts:google-java-format (190 packages loaded, 2132 targets configured) 1835: �[32m[1 / 1]�[0m checking cached actions 1836: �[32mINFO: �[0mRepository rules_jvm_external~~maven~maven instantiated at: 1837: <builtin>: in <toplevel> 1838: Repository rule pinned_coursier_fetch defined at: 1839: /home/runner/.bazel/external/rules_jvm_external~/coursier.bzl:1324:40: in <toplevel> 1840: �[31m�[1mERROR: �[0mAn error occurred during the fetch of repository 'rules_jvm_external~~maven~maven': 1841: Traceback (most recent call last): 1842: File "/home/runner/.bazel/external/rules_jvm_external~/coursier.bzl", line 517, column 21, in _pinned_coursier_fetch_impl 1843: fail("%s_install.json contains an invalid input signature and must be regenerated. " % (user_provided_name) + 1844: Error in fail: maven_install.json contains an invalid input signature and must be regenerated. This typically happens when the maven_install artifacts have been changed but not repinned. PLEASE DO NOT MODIFY THIS FILE DIRECTLY! To generate a new maven_install.json and re-pin the artifacts, please run: 1845: REPIN=1 bazel run @maven//:pin 1846: �[31m�[1mERROR: �[0mno such package '@@rules_jvm_external~~maven~maven//': maven_install.json contains an invalid input signature and must be regenerated. This typically happens when the maven_install artifacts have been changed but not repinned. PLEASE DO NOT MODIFY THIS FILE DIRECTLY! To generate a new maven_install.json and re-pin the artifacts, please run: 1847: REPIN=1 bazel run @maven//:pin 1848: �[31m�[1mERROR: �[0m/home/runner/work/selenium/selenium/scripts/BUILD.bazel:35:12: //scripts:google-java-format depends on @@rules_jvm_external~~maven~maven//:com_google_googlejavaformat_google_java_format in repository @@rules_jvm_external~~maven~maven which failed to fetch. no such package '@@rules_jvm_external~~maven~maven//': maven_install.json contains an invalid input signature and must be regenerated. This typically happens when the maven_install artifacts have been changed but not repinned. PLEASE DO NOT MODIFY THIS FILE DIRECTLY! To generate a new maven_install.json and re-pin the artifacts, please run: 1849: REPIN=1 bazel run @maven//:pin 1850: �[31m�[1mERROR: �[0mAnalysis of target '//scripts:google-java-format' failed; build aborted: Analysis failed 1851: �[32mINFO: �[0mElapsed time: 35.487s, Critical Path: 0.06s 1852: �[32mINFO: �[0m1 process: 1 internal. 1853: �[31m�[1mERROR: �[0mBuild did NOT complete successfully 1854: �[31m�[1mFAILED:�[0m 1855: �[31m�[1mERROR: �[0mBuild failed. Not running target 1856: �[0m 1857: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.