Add versions properties to cache

[Endi327]

Description:
When using refreshVersions plugin, all the versions are managed in one particular file called versions.properties. This file is created by the plugin in the root directory and only used for handling versions in one place. As you can see they have quite a huge user base, so this would help a lot of users.

This PR adds the files **/versions.properties to the cache key calculation (in addition to the existing **/.gradle, **/gradle-wrapper.properties).

Related issue:
None.

Check list:

• Mark if documentation changes are required.
• Mark if tests were added or updated to cover the changes.

[dmitry-shibanov]

Hello @Endi327. Thank you for your pull request. I think it looks good, just some minor questions.

• Does the pull request related to Include version catalog file in filehash in the Gradle cache key #237 ?
• Do you know how often file is changed ?
• If it's possible, could you please attach public repository for testing purposes.

[Endi327]

Hello @dmitry-shibanov. Thank you for your reply. Let me answer your questions:

• Does the pull request related to Include version catalog file in filehash in the Gradle cache key Include version catalog file in filehash in the Gradle cache key #237 ? -> The basic idea is the same, we would like to handle all versions in one specific file. However, Include version catalog file in filehash in the Gradle cache key #237 is about using version catalog and my PR is about using refreshVersions plugin or handling all dependency version in versions.properties file.
• Do you know how often file is changed ? -> It will change every time we add a new dependency or looking for updates and run ./gradlew refreshVersions.
• If it's possible, could you please attach public repository for testing purposes. -> Yes, I have a public repository: https://github.com/Endi327/fortnightly/tree/feature/refreshVersions. I already configured the refreshVersion plugin and to use my forked version of actions/setup-java.

[dmitry-shibanov]

Hello @Endi327. Thank you for your response. About the second question I'm just curious about it because I do not want to cause constant saving of the cache. It'll lead to the longer builds. How often will the ./gradlew refreshVersions command be used ?
I'll test with your changes. For now I'll start up checks on the CI.
Thank you!

[dmitry-shibanov]

Could you please run the npm run format command.

[Endi327]

@dmitry-shibanov It is depending on the team/developer. It is possible that it will run every time before creating a new pull request, but the file will only change if the task find a new available version for one of the 3rd party dependencies. So there is no exact method to count the frequency because all dependency has its own schedule for updates. We will create an action to run it every two weeks.
I updated my project with a fix, please use the latest commit (b271e04ed9d60ce8042a7c5cfbedfa2584d48d50) as head on feature/refreshVersion.
I also updated my pull request with the lint fix, npm run format pointed out the issue.

[Endi327]

@dmitry-shibanov Updated the unit tests so now all checks have passed.

[Endi327]

@dmitry-shibanov Is there any update on this?

[dmitry-shibanov]

Hello @Endi327. Sorry for the late response. Could you please sync with the main branch ?