Jersey update from 3.1.8 to 3.1.9 performance regression when using the JVM `http.proxyHost` mechanism

[ripdajacker]

This PR introduced the regression: #5749

The referenced fix introduces a map from java.util.URL to a Lock. That has the side effect of calling getInetAddress(url.host), which significantly impacts the performance if you are running the JVM with a proxy with -Dhttp.proxyHost and -Dhttp.proxyPort.

Before the call to hashCode the JVM handled the proxy connection transparently.

[ripdajacker]

Fixed in: #5815

[jansupol]

Fixed by #5794