Fix ./gradlew build on kafka

[Abacn]

Although we no longer run ./gradlew build on Jenkins tests (#27320), it is still exercised by IDEs (like IntelliJ) when project load or hit the "Build" button, and could cause confusion for new contributors

Please add a meaningful description for your change here

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[Abacn]

Command: ./gradlew -p sdks/java/io/kafka/ build

Previous:

> Task :sdks:java:io:kafka:kafka-211:analyzeClassesDependencies FAILED
> Task :sdks:java:io:kafka:kafka-222:analyzeClassesDependencies FAILED
> Task :sdks:java:io:kafka:kafka-111:analyzeClassesDependencies FAILED
> Task :sdks:java:io:kafka:kafka-251:analyzeClassesDependencies FAILED
> Task :sdks:java:io:kafka:kafka-231:analyzeClassesDependencies FAILED
> Task :sdks:java:io:kafka:kafka-241:analyzeClassesDependencies FAILED
> Task :sdks:java:io:kafka:kafka-01103:analyzeClassesDependencies FAILED
> Task :sdks:java:io:kafka:kafka-201:analyzeClassesDependencies FAILED
> Task :sdks:java:io:kafka:kafka-100:analyzeClassesDependencies FAILED

FAILURE: Build completed with 9 failures.

Now:

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.6.2/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 16s

[Abacn]

R: @johnjcasey @bvolpato

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control

[bvolpato]

I do ./gradlew build locally too for a quick general check on a change! This will be helpful, thanks Yi