Can't open browser with 'o' shortcut when using --host option

[mempf]

Describe the bug

When using the Vite 4.4.0 branch/4.4.0-beta.0 release and setting the --host option the shortcut to open the browser with 'o' does not work and returns the following message instead:
No URL available to open in browser

VITE v4.4.0-beta.0  ready in 664 ms

  ➜  Network: http://192.168.0.100:5173/
  ➜  press h to show help
No URL available to open in browser

The same message occurs if the "open" option is used to attempt to open a browser automatically on startup.

It appears this issue started to occur after this commit and the issue goes away if reverted: 505f0b9

This issue seems to occur because when a --host is specified we no longer have a "local" address in the "resolvedUrls" used here:

vite/packages/vite/src/node/server/index.ts

Line 438 in 1a0c806

const url = server.resolvedUrls?.local[0]

Perhaps simply looking at the "network" addresses for a resolvedUrl if the "local" list is empty is all that is needed:
const url = server.resolvedUrls?.local[0] ?? server.resolvedUrls?.network[0]

Reproduction

https://stackblitz.com/edit/vitejs-vite-ccink3?file=package.json&terminal=dev

Steps to reproduce

A minimal example has been included. T
o trigger the issue simply:

1. Set the --host option to a value that is not localhost, 127.0.0.1 or 0.0.0.0. For example --host 192.168.0.100
2. Press 'o' once vite opens
3. Observe that the message "No URL available to open in browser" is display instead of the browser opening.

System Info

System:
    OS: Linux 5.15 Linux Mint 21.1 (Vera)
    Memory: 5.39 GB / 10.97 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 16.20.0 - ~/.nvm/versions/node/v16.20.0/bin/node
    npm: 8.19.4 - ~/.nvm/versions/node/v16.20.0/bin/npm
  Browsers:
    Chrome: 114.0.5735.133
    Firefox: 114.0.2
  npmPackages:
    vite: ^4.4.0-beta.0 => 4.4.0-beta.0

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• vitejs-vite-ccink3 (Open reproduction)

[bluwy]

Perhaps simply looking at the "network" addresses for a resolvedUrl if the "local" list is empty is all that is needed:
const url = server.resolvedUrls?.local[0] ?? server.resolvedUrls?.network[0]

I think this make sense. Feel free to send a PR!