Support Gradle Remote Build Cache

See https://community.atlassian.com/t5/Bitbucket-Pipelines-questions/How-to-setup-Gradle-Remote-Build-Cache/qaq-p/981395?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_answer&utm_content=topic

Bitbucket pipeline has a mechanism in place that allows to save and restore the Gradle cache directory. We work with larger projects (following the mono-repository) approach, where it approach may not scale too well. A Gradle cache grows rather quickly and it takes substantial resources already to just pack/unpack the Gradle cache. Moreover, different steps in the pipeline may only need small parts of it.

It would be desirable to have support for https://proandroiddev.com/speed-up-your-build-with-gradle-remote-build-cache-2ee9bfa4e18. As it allows to incrementelly check whether a given task has already been performed.

A simple HTTP repository would already suffice for it. In other project we made use of Artifactory generic repositories for this purpose. Alternatively it would be interesting to have support for repositories in general, meaning generic HTTP, Docker and Maven similar to others like GitLab and Azure DevOps where it is a built-in feature as well.