fix(vite): remove default for hmr from schema.json

[mandarini]

The reason for this change is the following:

If there's a default set in schema.json, then the default can ONLY be overwritten in project.json or if the user passes the option through a flag (eg: nx serve my-app --hmr=false). It cannot be overwritten in vite.config.ts. I think it's best to allow the user to be able to set all options in vite.config.ts if they want to. So it's best to not impose any defaults.

In this PR, I am adding the hmr: true in project.json, so a user can either change it there, or remove it completely, and set it in vite.config.ts.

[vercel]

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

Name	Status	Preview	Updated
nx-dev	✅ Ready (Inspect)	Visit Preview	Dec 6, 2022 at 0:38AM (UTC)

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit a52c6ae. 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 11 targets

• nx affected --target=e2e --base=5d910c0f1a9ec3ba6d7ebd78072af5cc5caf86c5 --head=a52c6ae7bacf833aa1bf832bcc74b68f14c7b156 --exclude=e2e-storybook,e2e-storybook-angular,e2e-react-native,e2e-detox --parallel=1
• nx affected --target=test --base=5d910c0f1a9ec3ba6d7ebd78072af5cc5caf86c5 --head=a52c6ae7bacf833aa1bf832bcc74b68f14c7b156 --parallel=1
• nx affected --target=build --base=5d910c0f1a9ec3ba6d7ebd78072af5cc5caf86c5 --head=a52c6ae7bacf833aa1bf832bcc74b68f14c7b156 --parallel=3
• nx depcheck --no-dte
• nx lint --no-dte
• nx check-lock-files --no-dte
• nx affected --target=lint --base=5d910c0f1a9ec3ba6d7ebd78072af5cc5caf86c5 --head=a52c6ae7bacf833aa1bf832bcc74b68f14c7b156 --parallel=3
• nx check-commit --no-dte
• nx-cloud record -- nx format:check --base=5d910c0f1a9ec3ba6d7ebd78072af5cc5caf86c5 --head=a52c6ae7bacf833aa1bf832bcc74b68f14c7b156
• nx check-imports --no-dte
• nx documentation --no-dte

---

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.