chore(deps): bump gradle-wrapper from 8.14.5 to 9.8.0

[dependabot]

Bumps gradle-wrapper from 8.14.5 to 9.8.0.

Release notes

Sourced from gradle-wrapper's releases.

9.8.0

The Gradle team is excited to announce Gradle 9.8.0.

Here are the highlights of this release:

• Java 27 support
• Maven mirror settings reuse
• Linked problem locations in build output

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle: Aman Gautam, Björn Kautler, Eng Zer Jun, Hashim Khan, Julian Krannich, KBS, Labh R Jethe, Mark Dodgson, Maxim, monkey, nataphon-ktsystems, Paul King, Qiu Tian, rg_sandesh, Roberto Perez Alcolea, Sean, Zongle Wang.

Upgrade instructions

Switch your build to use Gradle 9.8.0 by updating your wrapper:

./gradlew :wrapper --gradle-version=9.8.0 && ./gradlew :wrapper

See the Gradle 9.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

9.8.0 RC3

The Gradle team is excited to announce Gradle 9.8.0 RC3.

Here are the highlights of this release:

... (truncated)

Commits

• a927be5 Add the Develocity plugin back to the Android smoke tests (#39273)
• eaee500 Add the Develocity plugin back to the Android smoke tests
• 189b672 Route everything still hitting Maven Central through the mirror (#39257)
• 36b1814 Add back mavenCentral to doc snippets
• 2740c2d Update Gradle wrapper to version 9.8.0-rc-3 (#39264)
• 2099383 Update Gradle wrapper to version 9.8.0-rc-3
• c80202f Route everything still hitting Maven Central through the mirror
• 3f6a534 Fix when a best practice was introduced (#39253)
• 9efc9ed Fix when a best practice was introduced
• 459e143 Route integration test dependencies through the repository mirror (#39239)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[github-actions]

Unit Test Results 🚀

0 tests   - 611   0 ✅  - 611   0s ⏱️ - 2m 5s
0 suites  -  54   0 💤 ±  0 
0 files    -  54   0 ❌ ±  0 

Results for commit 9130d1f. ± Comparison against base commit 9f7c460.

[github-actions]

The scan step did not produce a report (outcome: skipped). See the workflow logs.
Result: FAILED — a dependency has a known vulnerability

Full run log

[github-actions]

Code coverage

module	lines	branches
sdk-java	no report	no report
sdk-java-ui	no report	no report

No coverage report was produced for: sdk-java, sdk-java-ui.

Build output (last 40 lines)

 - Maven mirror settings reuse
 - Linked problem locations in build output

For more details see https://docs.gradle.org/9.8.0/release-notes.html

Starting a Gradle Daemon (subsequent builds will be faster)
gradle/actions: Writing build results to /home/runner/work/_temp/.gradle-actions/build-results/gradle-1790592994609.json

[Incubating] Problems report is available at: file:///home/runner/work/countly-sdk-java/countly-sdk-java/build/reports/problems/problems-report.html

FAILURE: Build failed with an exception.

* Where:
Build file '/home/runner/work/countly-sdk-java/countly-sdk-java/build.gradle' line: 132

* What went wrong:
Groovy DSL script compilation problem
  Could not compile build file '/home/runner/work/countly-sdk-java/countly-sdk-java/build.gradle'.
    Location: /home/runner/work/countly-sdk-java/countly-sdk-java/build.gradle:132
> startup failed:
  build file '/home/runner/work/countly-sdk-java/countly-sdk-java/build.gradle': 132: unable to resolve class XmlParser
   @ line 132, column 19.
           def suite = new XmlParser(false, false).parse(file)
                       ^

  build file '/home/runner/work/countly-sdk-java/countly-sdk-java/build.gradle': 148: unable to resolve class XmlParser
   @ line 148, column 16.
       def parser = new XmlParser(false, false)
                    ^

  2 errors


* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights from a Build Scan (powered by Develocity).
> Get more help at https://help.gradle.org.

BUILD FAILED in 7s

Full run log

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.