fix: deploy to hanzo namespace instead of bootnode to avoid duplicate resources

Replace kubectl apply of full manifests (which created conflicting
resources in the bootnode namespace) with kubectl set image targeting
the existing deployments in the hanzo namespace. This eliminates
duplicate ingresses and image pull failures.

.github/workflows/ci.yml

@@ -206,16 +206,13 @@ jobs:
       - name: Save DigitalOcean kubeconfig
         run: doctl kubernetes cluster kubeconfig save ${{ secrets.K8S_CLUSTER_NAME }}
 
+      - name: Get short SHA
+        id: deploy-sha
+        run: echo "short=$(git rev-parse --short HEAD)" >> $GITHUB_OUTPUT
+
       - name: Deploy to Kubernetes
         run: |
-          kubectl apply -f infra/k8s/namespace.yaml
-          kubectl apply -f infra/k8s/api-deployment.yaml
-          kubectl apply -f infra/k8s/hanzo-web3-deployment.yaml
-          kubectl apply -f infra/k8s/bootnode-web-deployment.yaml
-          kubectl apply -f infra/k8s/ingress.yaml
-          kubectl rollout restart deployment/bootnode-api -n bootnode
-          kubectl rollout restart deployment/hanzo-web3 -n bootnode
-          kubectl rollout restart deployment/bootnode-web -n bootnode
-          kubectl rollout status deployment/bootnode-api -n bootnode --timeout=300s
-          kubectl rollout status deployment/hanzo-web3 -n bootnode --timeout=300s
-          kubectl rollout status deployment/bootnode-web -n bootnode --timeout=300s
+          kubectl set image deployment/bootnode-web -n hanzo web=${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:web-${{ steps.deploy-sha.outputs.short }}
+          kubectl set image deployment/bootnode -n hanzo bootnode=${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:api-${{ steps.deploy-sha.outputs.short }}
+          kubectl rollout status deployment/bootnode-web -n hanzo --timeout=300s
+          kubectl rollout status deployment/bootnode -n hanzo --timeout=300s