Draft: Different handling of Gradle build tool vs. build process artifacts with...

What does this MR do?

As far as I understand chapter Cache vs artifacts it would be a better fit to handle Gradle tool and execution "artifacts" (like 3rd-party dependencies, or Gradle itself, especially if using Gradle Wrapper) as content to cache (especially to cache them between executions of pipelines).

Only artifacts of the build process itself (like compiled classes, deployment artifacts like JARs or Docker images) should be considered as GitLab CI artifacts to push them from stage to stage during a single pipeline run; and not between different executions of pipeline.

"build" job artifacts should expire relatively short-termed to live only till next job ramps up. "test" job artifacts expiration should give somebody the chance to look at e.g. test reports.