Implement cache capabilities for CI Pipelines

[SergK]

We must ensure the build cache is updated to speed up CI pipelines. At the same time, the implementation should be cloud-agnostic and doesn't depend on the specific platform. We can go two ways here:

• use the snapshot approach (using Kubernetes driver - and this is another stream we are going to follow) or
• store cache on some HTTP server that serves cache distribution and is closer to the pipeline resources. Leverage capabilities of https://github.com/chmouel/go-simple-uploader/tree/master. A good description is provided in the article https://blog.chmouel.com/2021/05/25/speed-up-your-tekton-pipeline-caching-the-hacky-way/

For this task, we are going to implement the second approach.
We have to avoid a lot of volume mounts since there is a limit to the number of mounted volumes per instance (for example, in EKS). Another point: Tekton doesn't allow mounting two PVC volumes to a task without disabling affinity assistance, see tektoncd/catalog#1187

So, the idea behind this is to use a single volume with a subpath. See example here

/ws/cache    <--- use for cache, either NPM, go, maven
   /source   <--- use to checkout