fix: allow binding when strictPort is set but wildcard port is in use

[Copilot]

When server.host is set to a specific IP (e.g. 127.0.20.4) and strictPort: true, Vite's port availability pre-check tests 0.0.0.0 and ::. If any service holds the same port on a different interface, this wildcard check fails and Vite incorrectly aborts — even when the configured host:port is free.

Changes

• packages/vite/src/node/http.ts: In httpServerStart, when strictPort is set and the wildcard pre-check fails, Vite now attempts to bind to the configured host:port directly before giving up. On success, a warning is emitted that another server may be running on a wildcard IP. On EADDRINUSE, falls back to the existing strictPort throw.

• packages/vite/src/node/__tests__/http.spec.ts: Added tests covering: strictPort: true allows binding when wildcard port is in use; warning is emitted in that case; error still thrown when the configured host port is also occupied.

Example

// vite.config.js — previously failed with "Port 80 is already in use"
// even when 127.0.20.4:80 was free (other services on 127.0.10.x:80)
export default defineConfig({
  server: {
    host: '127.0.20.4',
    port: 80,
    strictPort: true,
  },
})