gha: Use ghcr.io for the k8s CI

Let's switch to using the `ghcr.io` registry for the k8s CI, as this
will save us some troubles on running the CI with PRs coming from forked
repos.

Fixes: #6587

Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>

.github/workflows/publish-kata-deploy-payload-s390x.yaml

@@ -6,11 +6,18 @@ on:
         required: false
         type: string
       registry:
-        repo: true
+        required: true
+        type: string
+      repo:
+        required: true
         type: string
       tag:
         required: true
         type: string
+      quay-io-login-continue-on-error:
+        required: false
+        type: boolean
+        default: false
 
 jobs:
   kata-payload:
@@ -33,10 +40,18 @@ jobs:
           registry: quay.io
           username: ${{ secrets.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
+        continue-on-error: ${{ inputs.quay-io-login-continue-on-error }}
+
+      - name: Login to Kata Containers ghcr.io
+        uses: docker/login-action@v2
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
 
       - name: build-and-push-kata-payload
         id: build-and-push-kata-payload
         run: |
           ./tools/packaging/kata-deploy/local-build/kata-deploy-build-and-upload-payload.sh \
           $(pwd)/kata-static.tar.xz \
-          quay.io/kata-containers/${{ inputs.repo }} ${{ inputs.tag }}
+          ${{ inputs.registry }}/${{ inputs.repo }} ${{ inputs.tag }}