java/net/Socket/B8312065.java failing on some machines for JDK11 and 17

java/net/Socket/B8312065.java is failing on some machines

```
12:32:08 configuration:
12:32:08 STDOUT:
12:32:08 SIGPIPE
12:32:08 STDERR:
12:32:08 java.net.SocketException: Network is unreachable (connect failed)
12:32:08 at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
12:32:08 at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:526)
12:32:08 at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:246)
12:32:08 at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:227)
12:32:08 at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
12:32:08 at java.base/java.net.Socket.connect(Socket.java:633)
```

Seen in the [JDK11](https://github.com/adoptium/aqa-tests/issues/7010#issuecomment-4273801060) and [17](https://github.com/adoptium/aqa-tests/issues/7009#issuecomment-4280688045) dryrun triage
Platforms affected: arm32 linux, aarch64 linux, ppc64le linux

The test expects to NOT connect to 192.168.255.255, to test the timeout capability. But on some platforms the address to which it wants to connect cannot be identified. The fix for this is https://github.com/openjdk/jdk11u/commit/f665ad7771e98a06b6fbf1fcfe3b4b92267a9bf9 which handles this case, but it is not a robust fix. Therefore I think this test should be excluded

Upstream issue https://bugs.openjdk.org/browse/JDK-8350540. Backport fix https://bugs.openjdk.org/browse/JDK-8365728 but this fix needs to handle `SocketException`

Start with java/net/Socket/B8312065.java and compare the JDK11 and JDK17 dryrun failures for the listed Linux platforms. Review the linked upstream issue and backport fix, paying particular attention to SocketException handling. Done means the test no longer fails on affected platforms while retaining its timeout coverage or being explicitly excluded as required.

Written by the indexing model from the issue text.