Update ciphers for TLSv1.3 and JDK11 if available

[jaymode]

This commit updates the default ciphers and TLS protocols that are used
when the runtime JDK supports them. New cipher support has been
introduced in JDK 11 and 12 along with performance fixes for AES GCM.
The ciphers are ordered with PFS ciphers being most preferred, then
AEAD ciphers, and finally those with mainstream hardware support. When
available stronger encryption is preferred for a given cipher.

This is a backport of #41385 and #41808. There are known JDK bugs with
TLSv1.3 that have been fixed in various versions. These are:

1. The JDK's bundled HttpsServer will endless loop under JDK11 and JDK
   12.0 (Fixed in 12.0.1) based on the way the Apache HttpClient performs
   a close (half close).
2. In all versions of JDK 11 and 12, the HttpsServer will endless loop
   when certificates are not trusted or another handshake error occurs. An
   email has been sent to the openjdk security-dev list and MockWebServer incompatible with HttpClient closing on TLSv1.3 #38646 is open
   to track this.
3. In JDK 11.0.2 and prior there is a race condition with session
   resumption that leads to handshake errors when multiple concurrent
   handshakes are going on between the same client and server. This bug
   does not appear when client authentication is in use. This is
   JDK-8213202, which was fixed in 11.0.3 and 12.0.
4. In JDK 11.0.2 and prior there is a bug where resumed TLS sessions do
   not retain peer certificate information. This is JDK-8212885.

The way these issues are addressed is that the current java version is
checked and used to determine the supported protocols for tests that
provoke these issues.

[elasticmachine]

Pinging @elastic/es-security

[tvernum]

👍 LGTM