RFR: 8236413: AbstractConnectTimeout should tolerate both NoRouteToHostException and UnresolvedAddressException

[Daniel Fuchs]

The timeout tests extending AbstractConnectTimeout have been relaxed to accept a
ConnectException wrapping NoRouteToHostException.
These test have been observed failing intermittently with ConnectException wrapping
java.nio.channels.UnresolvedAddressException instead - presumably a transient network
failure caused this other exception to be thrown.

The test logic should be relaxed to accept UnresolvedAddressException as possible
cause in ConnectException too.

-------------

Commit messages:
 - 8236413: AbstractConnectTimeout should tolerate both NoRouteToHostException and UnresolvedAddressException
 - 8236413: AbstractConnectTimeout should tolerate both NoRouteToHostException and UnresolvedAddressException

Changes: https://git.openjdk.java.net/jdk/pull/1629/files
 Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=1629&range=00
  Issue: https://bugs.openjdk.java.net/browse/JDK-8236413
  Stats: 14 lines in 1 file changed: 7 ins; 0 del; 7 mod
  Patch: https://git.openjdk.java.net/jdk/pull/1629.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk pull/1629/head:pull/1629

PR: https://git.openjdk.java.net/jdk/pull/1629