Gradle 8.2: work around fix for release publishing

[TWiStErRob]

Missed a spot in :test warnings and workaround for shipkit/shipkit-changelog#103 triggered by https://github.com/mockito/mockito/actions/runs/5457593285/jobs/9931914322

See #3051 (comment)

Testing

I was able to get past the problem shown in the CI by setting env vars and applying the workaround. The failure is now at real publishing, so it should be ok 🤞:

$ set NEXUS_TOKEN_USER=bad
$ set NEXUS_TOKEN_PWD=bad
$ gradlew githubRelease publishToSonatype closeAndReleaseStagingRepository releaseSummary

> Task :bom:publishJavaLibraryPublicationToSonatypeRepository FAILED
> Task :junit-jupiter:publishJavaLibraryPublicationToSonatypeRepository FAILED
> Task :proxy:publishJavaLibraryPublicationToSonatypeRepository FAILED
> Task :subclass:publishJavaLibraryPublicationToSonatypeRepository FAILED
> Task :errorprone:publishJavaLibraryPublicationToSonatypeRepository FAILED
> Task :android:publishJavaLibraryPublicationToSonatypeRepository FAILED
> Task :publishJavaLibraryPublicationToSonatypeRepository FAILED

all failures: Received status code 401 from server: Unauthorized

Checklist

• Read the contributing guide
• PR should be motivated, i.e. what does it fix, why, and if relevant how
• If possible / relevant include an example in the description, that could help all readers
  including project members to get a better picture of the change
• Avoid other runtime dependencies
• Meaningful commit history ; intention is important please rebase your commit history so that each
  commit is meaningful and help the people that will explore a change in 2 years
• The pull request follows coding style
• Mention Fixes #<issue number> in the description if relevant
• At least one commit should mention Fixes #<issue number> if relevant

[TimvdLippe]

Thanks!