fix(github-actions): pin buildx to v0.11.2

[nitrocode]

what

• fix(github-actions): pin buildx to v0.11.2

why

• resolve intermittent build failures
• at one point we did not have a pin, which gave us many build failures. Then we pinned to v0.10.6 and experienced no build failures. Then buildkit released a fix in v0.11.2 and instead of pinning, we removed the pin to use the latest again. I think a recent release maybe v0.11.6 or earlier caused a regression, albeit rare.
• if pinning to v0.11.2 doesn't resolve this then we pin to v0.10.6 again

tests

• I have tested my changes by reading docs and references and testing in this pr

references

• buildx failed with: ERROR: failed to solve: failed to push ghcr.io/finchsec/kali:latest: failed to copy: io: read/write on closed pipe docker/build-push-action#761 (comment)
• buildx failed with: ERROR: failed to solve: failed to push ghcr.io/finchsec/kali:latest: failed to copy: io: read/write on closed pipe docker/build-push-action#761 (comment)
• https://github.com/runatlantis/atlantis/actions/runs/5139979174/jobs/9250992369
• previous pr build(docker): fix intermittent ghcr push failures #3018 (pin to v0.10.6) and feat(build): add new sha ghrc docker tags using docker/metadata-action #3121 (remove pin)
• https://github.com/moby/buildkit/releases/tag/v0.11.6 (latest and assumption is that this release or a recent release causes this error)
• https://github.com/moby/buildkit/releases/tag/v0.11.2 (contains bug fix)
• https://github.com/moby/buildkit/releases/tag/v0.10.6 (last working release before first set if failures)

[nitrocode]

cc: @jamengual @GenPage please review. This is a pretty tiny PR.