drop the scaffold vendor's build plugin, still in the build config

vite.config.ts imported componentTagger from the scaffold vendor's plugin and package.json
carried the dependency. It only ran in dev mode, so it never reached a
production byte — but it is the vendor's fingerprint in the build of a Hanzo
host, and it pulls 837 lines of lockfile for a plugin nobody here uses. The
the scaffold generator's CDN script tag it came with is already gone from index.html.

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

package.json

@@ -75,7 +75,6 @@
     "eslint-plugin-react-hooks": "^5.1.0-rc.0",
     "eslint-plugin-react-refresh": "^0.4.9",
     "globals": "^15.9.0",
-    "component-tagger": "^1.1.3",
     "postcss": "^8.4.47",
     "tailwindcss": "^4.0.17",
     "typescript": "^5.5.3",

vite.config.ts

@@ -1,23 +1,19 @@
 import { defineConfig } from "vite";
 import react from "@vitejs/plugin-react-swc";
 import path from "path";
-import { componentTagger } from "component-tagger";
 
 // https://vitejs.dev/config/
-export default defineConfig(({ mode }) => ({
+export default defineConfig({
   // Use relative paths for assets - works on both custom domain and github.io
   base: './',
   server: {
     host: "::",
     port: 8080,
   },
-  plugins: [
-    react(),
-    mode === 'development' && componentTagger(),
-  ].filter(Boolean),
+  plugins: [react()],
   resolve: {
     alias: {
       "@": path.resolve(__dirname, "./src"),
     },
   },
-}));
+});