fix(dev): pin hub port to 5173 with strictPort

The 7 standalone vite configs had server.port + strictPort: true
since commit 9a1e5e3, but the hub config was left on the default
auto-incrementing 5173. When something briefly held 5173 (an
orphaned vite process from a crashed restart, an ENOENT during
concurrent dep optimization, etc.) the hub silently drifted to
5174. The browser's cached SW kept loading the page from
localhost:5173, all in-page asset fetches died with
ERR_CONNECTION_REFUSED, and chakra navigation appeared broken.

Pinning the hub the same way the standalones are pinned eliminates
that drift. If 5173 is genuinely held when dev:all starts, vite
will fail loud (and the user can free the port) instead of moving
the hub silently.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

vite.config.ts

@@ -9,6 +9,10 @@ import { visualizer } from 'rollup-plugin-visualizer'
 
 // https://vite.dev/config/
 export default defineConfig(({ mode }) => ({
+  server: {
+    port: 5173,
+    strictPort: true,
+  },
   plugins: [
     vue(),
     tailwindcss(),