feat(vite): pin Vite version range to patch releases only to avoid conflicts with Angular

[jaysoo]

This PR changes the version range for Vite packages to only include patch releases. Updating to latest minor may cause breakage if Angular devkit is still using the previous minor.

If you run pnpm why vite for the failing workspace you'll see this:

      @nx/angular 17.0.0
      └─┬ @angular-devkit/build-angular 16.1.4 peer
        ├─┬ @vitejs/plugin-basic-ssl 1.0.1
        │ └── vite 4.3.9 peer
        └── vite 4.3.9
      @nx/vite 17.0.0
      ├── vite 4.3.9 peer
      └─┬ vitest 0.32.0 peer
        ├── vite 4.4.1
        └─┬ vite-node 0.32.0
          └── vite 4.4.1
      @vitejs/plugin-react 4.0.0
      └── vite 4.3.9 peer
      @vitest/coverage-c8 0.32.0
      └─┬ vitest 0.32.0 peer
        ├── vite 4.4.1
        └─┬ vite-node 0.32.0
          └── vite 4.4.1
      @vitest/ui 0.32.0
      └─┬ vitest 0.32.0 peer
        ├── vite 4.4.1
        └─┬ vite-node 0.32.0
          └── vite 4.4.1
      vite 4.3.9
      vite-plugin-dts 2.3.0
      └── vite 4.3.9 peer
      vite-tsconfig-paths 4.2.0
      └── vite 4.3.9 peer
      vitest 0.32.0
      ├── vite 4.4.1
      └─┬ vite-node 0.32.0
        └── vite 4.4.1

Current Behavior

e2e tests are failing (e.g. https://staging.nx.app/runs/RvNeUFFbhV)

Expected Behavior

e2e tests should pass

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 7, 2023 3:16am

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 9704a4e. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 1 target

• nx affected -t e2e-macos --parallel=1 --base=5af5e6ca91eca112d3dc0cf89565284575749135 --head=9704a4e3525fafcf5f4d61bd9f2ee2d010e4cb40

---

Sent with 💌 from NxCloud.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.