feat!(action/docker/build-image): use gha cache backend

[neilime]

No description provided.

[NikitaCOEUR]

@neilime
It is marked in the definition of release 0.21.0 :

Since 0.19.0, docker-build-images is using gha backend cache, so no more cache image (ghcr.io/my-org/my-repo/my-image/cache) are created in the registry. It is reasonable to delete the existing one are they are useless.

But here, there's still the definition of the image to be cached with the /cache mention, is that normal?
https://github.com/hoverkraft-tech/ci-github-container/pull/335/files#diff-b1a31054574d361286a45d0269d77a0c0845e02d0ff84821308827c5e370a869L142

Does the cache still work? We're having trouble explaining the behavior of layers that are replayed between two pushes on the same PR and that logically shouldn't be played...

[neilime]

@NikitaCOEUR, you're right. There was a extra "/cache" in the image name, not sure it was a problem as the cache backend was using this for fetching and pulling cache, but we have fixed it to avoid confusion.

As some people asked for it, we have added an option to choose the cache backend type: https://github.com/hoverkraft-tech/ci-github-container/releases/tag/0.22.0