pars runs the explorer everyone else runs

It pulled ghcr.io/parsdao/explore, an image whose repository does not
resolve, and sat in ImagePullBackOff while the other four chains ran the
same luxfi/explore image branded by their own configmap. A second image for
a frontend that is already configured per chain is a second thing to keep
current, and this one was never current.

Co-authored-by: Hanzo AI <[email protected]>

deploy/lux-mainnet/explore-fe-pars.yaml

@@ -1,8 +1,3 @@
-# The RUNTIME environment, and only that. luxfi/explore's .env.example.lux
-# mixes build-time and runtime variables in one file -- NEXT_PUBLIC_BRAND is
-# read by `pnpm build`, and the branding, marketplace and homepage URLs were
-# dropped from the image -- so feeding that file to the container fails the
-# validator outright. These are the variables v2.8.1-lux accepts.
 cd:
   automated: false
 replicas: 1
@@ -12,9 +7,9 @@ selectorLabels:
   network: mainnet
 containerName: explore
 image:
-  repository: ghcr.io/parsdao/explore
-  tag: v1.1.30
-  digest: sha256:ff7e2011f4e0e684ac0c2855ad482fdde8c03dac3cdb50a38c38dadd4b53317f
+  repository: ghcr.io/luxfi/explore
+  tag: v2.8.1-lux
+  digest: sha256:c4a75d036d7d7f93b870f7c1d3b9876b3b1c3e34063c11b90f68189554706193
   pullPolicy: IfNotPresent
 labels:
   brand: pars