Update dependency net.bytebuddy:byte-buddy to v1.15.10

[renovate]

This PR contains the following updates:

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

---

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 d25aafe)

Action: Format / Check format script run

Failed stage: Run Bazel [❌]

Failure summary: The action failed due to issues with the maven_install.json file: The file contains an invalid input signature and must be regenerated. This error typically occurs when the maven_install artifacts have been changed but not repinned. The log suggests running REPIN=1 bazel run @maven//:pin to regenerate and re-pin the artifacts. As a result, the build process could not fetch the necessary dependencies, leading to a failure in analyzing the target //scripts:google-java-format.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 970: Package 'php-symfony-debug-bundle' is not installed, so not removed 971: Package 'php-symfony-dependency-injection' is not installed, so not removed 972: Package 'php-symfony-deprecation-contracts' is not installed, so not removed 973: Package 'php-symfony-discord-notifier' is not installed, so not removed 974: Package 'php-symfony-doctrine-bridge' is not installed, so not removed 975: Package 'php-symfony-doctrine-messenger' is not installed, so not removed 976: Package 'php-symfony-dom-crawler' is not installed, so not removed 977: Package 'php-symfony-dotenv' is not installed, so not removed 978: Package 'php-symfony-error-handler' is not installed, so not removed ... 1771: com.google.code.gson:gson has multiple versions 2.11.0, 2.8.9 1772: com.google.guava:guava has multiple versions 33.3.1-jre, 31.1-jre 1773: org.mockito:mockito-core has multiple versions 5.14.2, 4.3.1 1774: Please remove duplicate artifacts from the artifact list so you do not get unexpected artifact versions 1775: �[32mINFO: �[0mRepository rules_jvm_external~~maven~maven instantiated at: 1776: <builtin>: in <toplevel> 1777: Repository rule pinned_coursier_fetch defined at: 1778: /home/runner/.bazel/external/rules_jvm_external~/coursier.bzl:1324:40: in <toplevel> 1779: �[31m�[1mERROR: �[0mAn error occurred during the fetch of repository 'rules_jvm_external~~maven~maven': 1780: Traceback (most recent call last): 1781: File "/home/runner/.bazel/external/rules_jvm_external~/coursier.bzl", line 517, column 21, in _pinned_coursier_fetch_impl 1782: fail("%s_install.json contains an invalid input signature and must be regenerated. " % (user_provided_name) + 1783: 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: 1784: REPIN=1 bazel run @maven//:pin 1785: �[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: 1786: REPIN=1 bazel run @maven//:pin 1787: �[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: 1788: REPIN=1 bazel run @maven//:pin 1789: �[32mAnalyzing:�[0m target //scripts:google-java-format (180 packages loaded, 1468 targets configured) 1790: �[32m[1 / 1]�[0m checking cached actions 1791: �[31m�[1mERROR: �[0mAnalysis of target '//scripts:google-java-format' failed; build aborted: Analysis failed 1792: �[32mINFO: �[0mElapsed time: 28.115s, Critical Path: 0.07s 1793: �[32mINFO: �[0m1 process: 1 internal. 1794: �[31m�[1mERROR: �[0mBuild did NOT complete successfully 1795: �[31m�[1mFAILED:�[0m 1796: �[31m�[1mERROR: �[0mBuild failed. Not running target 1797: �[0m 1798: ##[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.

[A1exKH]

Code LGTM. Please check the reason for failed checks in PR.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.