Migrate to setup-gradle@v3

[TWiStErRob]

Proposed commit message:

Migrate from gradle-build-action to setup-gradle GitHub Action.

A new way of consuming Gradle Actions is coming in v3.
There are no significant changes to the action logic,
the v3 version and the new action is a drop-in replacement.

Setting up AND running Gradle in the same step is deprecated,
so the steps are split into two: setup-gradle + `run:`.

Because `run:` uses different shells on different OSs,
the `-Pa=b` Gradle params are moved to `ORG_GRADLE_PROJECT_a: b`
environment variables, because that approach is fully cross platform.

Removed `cache: 'gradle'` from setup-java,
because setup-gradle is doing the same, and more.

PR: #803

---

PR checklist

The following checklist shall help the PR's author, the reviewers and maintainers to ensure the quality of this project.
It is based on our contributors guidelines, especially the "writing code" section.
It shall help to check for completion of the listed points.
If a point does not apply to the given PR's changes, the corresponding entry can be simply marked as done.

Documentation (general)

• There is documentation (Javadoc and site documentation; added or updated)
• There is implementation information to describe why a non-obvious source code / solution got implemented
• Site documentation has its own .adoc file in the docs folder, e.g. docs/report-entries.adoc
• Site documentation in .adoc file references demo in src/demo/java instead of containing code blocks as text
• Only one sentence per line (especially in .adoc files)
• Javadoc uses formal style, while sites documentation may use informal style

Documentation (new extension)

• The docs/docs-nav.yml navigation has an entry for the new extension
• The package-info.java contains information about the new extension

Code (general)

• Code adheres to code style, naming conventions etc.
• Successful tests cover all changes
• There are checks which validate correct / false usage / configuration of a functionality and there are tests to verify those checks
• Tests use AssertJ or our own PioneerAssert (which are based on AssertJ)

Code (new package)

• The new package is exported in module-info.java
• The new package is also present in the tests
• The new package is opened for reflection to JUnit 5 in module-info.java
• The new package is listed in the contribution guide

Contributing

• A prepared commit message exists
• The list of contributions inside README.adoc mentions the new contribution (real name optional)

[Michael1993]

It seems there is a difference between "uses-with-arguments" and "run" because the build fails when resolving input parameters. Could you look into that?

EDIT: Could be the difference between gradle and gradlew?

No, because the failing build is not one you changed, sorry.

[TWiStErRob]

Note: there was a weird random failure at https://github.com/junit-pioneer/junit-pioneer/actions/runs/7687474915/job/20947604357, never seen the like of it, I don't think it's related to this change. I reopened the PR to re-trigger and it "just worked": https://github.com/junit-pioneer/junit-pioneer/actions/runs/7688177222

[TWiStErRob]

Reopening to trigger on stable.

[TWiStErRob]

Reopening to trigger again on stable,
GitHub Actions Runner internal errored:
https://github.com/junit-pioneer/junit-pioneer/actions/runs/7733227001?pr=803

[Bukama]

@TWiStErRob Please give a short comment, when you think you are done. I've lost the context due your close/reopen-trigger actions ;)

[TWiStErRob]

It's done, same as 5 days ago, the reopening is only a substitution for my inability to press "Rerun all jobs" on the GitHub UI to test newer and newer versions getting released.