ci: skip canary deploy, kubeconfig, and k8s promotion (RBAC not ready) (#41)

- Remove kubectl install from dependencies (nothing uses it now)
- Skip Setup kubeconfig step
- Comment out k8s rolling update promotion
- Tag :latest still works (docker tag+push, no kubectl)
- Re-enable when ci-tekton-trigger SA has pod create/delete RBAC

---------

Co-authored-by: Admin Bot <[email protected]>
Reviewed-on: #41

.gitea/workflows/ci.yaml

@@ -60,7 +60,7 @@ jobs:
       # (Temporal, Gotify). Tests run against its pod IP directly.
       # Zero downtime: production pods untouched until tests pass.
       - name: Setup kubeconfig
-        if: false  # SKIP: only needed for canary deploy
+        if: false  # SKIP: only needed for canary deploy, RBAC not ready
         run: |
           mkdir -p ~/.kube
           echo "${KUBECONFIG_B64}" | base64 -d > ~/.kube/config
@@ -170,7 +170,7 @@ jobs:
       # ── Zero-downtime promotion ──────────────────────────────
       # kubectl set image triggers a rolling update: new pods come up
       # before old pods are terminated. Production traffic uninterrupted.
-      # TODO: Re-enable k8s rolling update when kubeconfig/RBAC is ready
+      # TODO: Re-enable rolling update when kubeconfig/RBAC is ready
       # - name: Promote — rolling update
       #   if: github.event_name == 'push' && github.ref == 'refs/heads/main'
       #   run: |