feat(repo): update vite to 5.2.x, @analogjs/* to 1.2.x, and update various supporting packages

PR Checklist

Please check if your PR fulfills the following requirements:

nx migrate latest
pnpm i
nx migrater --run-migrations

nx migrate @ngtools/webpack
nx migrate @angular/cli
nx migrate @angular/core

nx run ui-storybook-e2e:e2e # all tests passed

# bump packages to latest versions
# ufo, zod, tslib, tailwind-merge, superjson, semver, rxjs, postgres, ohash, ofetch, @types/node, @types/prismjs, axe-core
# postcss, postcss-preset-env, postcss-import, autoprefixer, prettier, prettier-plugin-tailwindcss, eslint-config-prettier, eslint-plugin-cypress
# ng-packagr, drizzle-kit, 
# vite, vite-tsconfig-paths, @swc/core, @swc/cli, @vitest/coverage-c8, @swc-node/register, rollup-plugin-visualizer

nx migrate ngx-sonner
nx migrate @analogjs/platform@latest

# removed @rollup/plugin-replace due to compatability issues; replaced with custom plugin
# moved rollup-plugin-typescript-paths to nitro.config.ts to make vite happy

nx run ui-storybook-e2e:e2e --skip-nx-cache # all tests passed
nx run app:serve # checked runtime on server, everything seems normal
nx run app:build --skip-nx-cache
nx run app:serve-nitro --skip-nx-cache

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[x] Feature
[x] Build related changes

Which package are you modifying?

I added repo as a commitlint option because I was doing repository maintenance. I can revert this and choose something else if you want that.

[x] repo

What is the current behavior?

Used older tooling

What is the new behavior?

Uses latest analogjs defaults like type: module in package.json and uses latest version of vite 5.2

Does this PR introduce a breaking change?

[x] No

goetzrobin / spartan

feat(repo): update vite to 5.2.x, @analogjs/* to 1.2.x, and update various supporting packages #264