Update Gradle Wrapper from 8.10.2 to 8.11

[github-actions]

Update Gradle Wrapper from 8.10.2 to 8.11.

Read the release notes: https://docs.gradle.org/8.11/release-notes.html

---

The checksums of the Wrapper JAR and the distribution binary have been successfully verified.

• Gradle release: 8.11
• Distribution (-bin) zip checksum: 57dafb5c2622c6cc08b993c85b7c06956a2f53536432a30ead46166dbca0f1e9
• Wrapper JAR Checksum: 2db75c40782f5e8ba1fc278a5574bab070adccb2d21ca5a6e5ed840888448046

You can find the reference checksum values at https://gradle.org/release-checksums/

---

🤖 This PR has been created by the Update Gradle Wrapper action.

Need help? 🤔

If something doesn't look right with this PR please file an issue here.

[david-allison]

Follow on from prep PR:

• Gradle 8.11 prep #442

[mikehardy]

🤔 I see the failure.

> Task :rsdroid-instrumented:processDebugManifestForPackage
    Blocking waiting for file lock on package cache

    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on build directory
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.[39](https://github.com/ankidroid/Anki-Android-Backend/actions/runs/11804996638/job/32886473938?pr=443#step:17:40)s
     Running `target/debug/build_rust`
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on build directory
    Finished `release` profile [optimized] target(s) in 1.05s
Error: No such file or directory (os error 2)

I noticed the "Blocking waiting for file lock on package cache" stuff while I was working on #442 specifically with the move to jaq install in gradle.

Will need to think on that one, I own it though (unless someone beats me to it - which is fine - just saying I will track it down...)

[mikehardy]

I took out the gradle.properties performance improvements and that did the trick. I was pretty sure I was closing out the cargo / jaq processes correctly (or, waiting on them, as it were) but I guess going parallel isn't something cargo can tolerate