RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v25]

[Volkan Yazıcı]

> This PR, addressing 8343791, changes `Socket::connect()` methods to close the `Socket` in the event that the connection cannot be established, the timeout expires before the connection is established, or the socket address is unresolved.
> 
> `tier3` tests pass against the 9f00f61d3b7fa42a5e23a04f80bb4bb1a2076ef2.

Volkan Yazıcı has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 39 commits:

 - Merge remote-tracking branch 'upstream/master' into Socket-CloseOnFailure-8343791
 - Capitalize `already connected` error message
 - Merge remote-tracking branch 'upstream/master' into Socket-CloseOnFailure-8343791
 - Remove redundant `ServerSocket` background consumer process
 - Use more fine-grained suppression
 - Further simplify tests
 - Extend `translateToSocketException()` with `AlreadyConnectedException`
 - Don't exceed 120 characters per line
 - Rework functional interfaces in tests
 - Use `ParameterizedTest` in `ConnectFailTest`
 - ... and 29 more: https://git.openjdk.org/jdk/compare/4da7c354...b6a2c8c9

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

Changes: https://git.openjdk.org/jdk/pull/22160/files
  Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22160&range=24
  Stats: 260 lines in 5 files changed: 218 ins; 33 del; 9 mod
  Patch: https://git.openjdk.org/jdk/pull/22160.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/22160/head:pull/22160

PR: https://git.openjdk.org/jdk/pull/22160