Cut release to address Node.js 16 deprecation warnings

[NotMyFault]

Hey @slawekjaranowski,

using s4u/setup-maven-action@v1.11.0 emits warnings on every workflow run due to the consumption of actions using Node.js 16 over 20, which is deprecated:

I took a brief look over the actions GH complains about:

• actions/setup-java: already addressed in https://github.com/s4u/setup-maven-action/pull/65
• s4u/maven-settings-action: already addressed in https://github.com/s4u/setup-maven-action/pull/66
• actions/cache: awaiting merge of https://github.com/s4u/setup-maven-action/pull/69
• stCarolas/setup-maven: awaiting merge of https://github.com/s4u/setup-maven-action/pull/70

Would you mind merging my PR linked above and cutting a release afterward? That would address the deprecation warning.

Thanks in advance!

[slawekjaranowski]

done https://github.com/s4u/setup-maven-action/releases/tag/v1.12.0

Thanks for report and PR

[NotMyFault]

done v1.12.0 (release)

Thanks for report and PR

I have to thank you for the swift merge and release, thanks! 🚀