Appetite for abstraction to other build environments

We use non-Github Actions CI pipelines for our build systems. We'd love to be able to contribute and leverage the existing tooling within the Gradle GitHub actions within other CI tools.

I wonder if there is appetite to refactor components of the GitHub actions to be published as npm packages and abstract the GitHub actions aspects away such that the common code can be reused within other environments.

I'd be willing to take on some of this refactoring as we would be able to reuse caching particularly in our environments!

The issue names no specific files, tests, or entry points. Review the existing Gradle GitHub Actions to identify caching and other reusable components, then determine which GitHub-specific parts can be separated and published as npm packages for other CI environments; done would require an agreed abstraction scope and reusable packages.

Written by the indexing model from the issue text.