Unresolved `InetAddress` if using hostname in `[servers]` section of configuration

Expected Behavior

It should resolve hostnames (e.g., localhost -> ::0) as the other program does.

Actual Behavior

It now has an unresolved InetAddress.

Steps to Reproduce

1. Add exampleserver = 'some-hostname-that-should-resolve-by-dns:25565' in [servers] section of velocity.toml.
2. Try to access the ServerInfo#getAddress() of exampleserver via any plugins in Velocity.
3. We have an unresolved InetAddress.

Plugin List

Velocity Version

[15:55:57 INFO]: Velocity 3.5.0-SNAPSHOT (git-d11511c1-b584)
[15:55:57 INFO]: Copyright 2018-2026 Velocity Contributors。Velocity 以 GNU 通用公共许可证第三版授权。
[15:55:57 INFO]: PaperMC - GitHub

Additional Information

Ref: https://github.com/PaperMC/Velocity/blob/d11511c18499497e7f7186211b109ef395b44acd/proxy/src/main/java/com/velocitypowered/proxy/util/AddressUtil.java#L44-L58
Why didn't we always resolve the hostname?

Start with proxy/src/main/java/com/velocitypowered/proxy/util/AddressUtil.java at lines 44-58, then trace how the [servers] section creates the ServerInfo exposed by ServerInfo#getAddress(). Compare the current behavior with the expected hostname resolution for localhost and DNS names. Done means configured hostnames provide resolved InetAddress values to plugins.