Recommend first party Gradle action instead of `cache: gradle`

[TWiStErRob]

Description:
Deprecate/remove cache: gradle option in favor of a first party Gradle action.
If this is not an option, at least mention gradle/actions/setup-gradle in the documentation AND action.yml description.

Justification:
setup-java tries to do too much. gradle/actions/setup-gradle (ex. gradle-build-action) is a fully featured, advanced GitHub Action for caching Gradle builds outputs. It now includes support for things that'll likely never be part of setup-java (e.g. configuration cache caching), leaving users confused and using potentially sub-optimal caching strategies. (example: gradle/gradle#13510 (comment))

Are you willing to submit a PR?
I'll let maintainers handle deprecations / removals, as that's a complex process.

[HarithaVattikuti]

Hello @TWiStErRob
Thank you for creating this feature request. We will investigate it and get back to you as soon as we have some feedback.

[daniel-shuy]

Relevent doc:
https://github.com/gradle/actions/blob/v3.4.2/docs/setup-gradle.md#incompatibility-with-other-caching-mechanisms

[trivikr]

Is there any update on this request?

The official GitHub docs for Java with Gradle recommend using gradle/actions/setup-gradle

[priya-kinthali]

Hello Everyone👋,
Thank you for your feedback and suggestions. We've updated the README as part of the merged PR#972 to highlight the use of gradle/actions/setup-gradle for advanced Gradle caching needs and to help users choose the most suitable caching solution for their projects.

Since this feature request has now been addressed, I will proceed to close the issue for now. Please feel free to reach out if you have any further questions or concerns. Thank you once again for your input and understanding!