fix(deps): update bytebuddy to v1.15.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
net.bytebuddy:byte-buddy-gradle-plugin	1.15.1 -> 1.15.2
net.bytebuddy:byte-buddy	1.15.1 -> 1.15.2

---

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 these updates again.

---

• If you want to rebase/retry this PR, check this box

---

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

[LikeTheSalad]

Skipping this version as it's causing this issue.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (1.15.2). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

[breedx-splk]

Ouch. Easily reproducible:

$ ./gradlew :instrumentation:httpurlconnection:testing:debugBytebuddyTransform
> Task :instrumentation:httpurlconnection:testing:debugBytebuddyTransform FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':instrumentation:httpurlconnection:testing:debugBytebuddyTransform'.
> Failed to resolve type description for io.opentelemetry.sdk.internal.Java9VersionSpecific=

I wonder if it might be related to raphw/byte-buddy#1710? I guess we just wait and try the next release with our fingers crossed? @LikeTheSalad what do you think?

[raphw]

I think I found the issue already. It's about Android not handling Multi-Release JAR files as a regular VM would do. Java9VersionSpecific is such a class. Seems like I need to suppress all MR classes on Android. I think it is working on master now, but I asked @LikeTheSalad to verify. If you can build from master and attempt, this would work, too.