fix: dev-remote hmr port override (#4163)

## Changes
<!-- Brief summary of your changes that is easy to understand -->
This removes the ability to override the hmr port in the vite config to
avoid breaking the system.

## Why
<!-- Why are these changes needed? Provide the context that the reviewer
might be missing.
For example, were there any decisions behind the change that are not
reflected in the code itself? -->

vite uses the same port for the server and hmr, so by just providing the
port override via flag which we already have it works fine.
The problem comes when a user overrides the vite.config.js file with
this

```
  server: {
    hmr: {
      port: 1234,
    },
  },
```

This breaks the system, and there's no reason the user will need that
when running the dev-remote command as we control it

## Tests
<!-- How have you tested the changes? -->

<!-- If your PR needs to be included in the release notes for next
release,
add a separate entry in NEXT_CHANGELOG.md as part of your PR. -->

Co-authored-by: MarioCadenas <[email protected]>

Author: MarioCadenas

cmd/workspace/apps/vite-server.js

@@ -48,6 +48,15 @@ async function startViteServer() {
       clientPath
     );
     const userConfig = loadedConfig?.config ?? {};
+
+    /**
+     * Vite uses the same port for the HMR server as the main server.
+     * Allowing the user to set this option breaks the system.
+     * By just providing the port override option, Vite will use the same port for the HMR server.
+     * Multiple servers will work, but if the user has this in their config we need to delete it.
+     */
+    delete userConfig.server?.hmr?.port;
+
     const coreConfig = {
       configFile: false,
       root: clientPath,