GEODE-10556: Fix SSL handshake failure in PulseSecurityWithSSLTest when JmxManagerBindAddress is empty

[JinwooHwang]

Problem

PulseSecurityWithSSLTest failed on GitHub Actions with authentication errors (BAD_CREDS) despite using correct credentials. Tests consistently passed locally but failed in CI:
SSLHandshakeException: No subject alternative names matching IP address 172.17.0.2 found

• PulseSecurityWithSSLTest > loginWithIncorrectAndThenCorrectPassword
• PulseSecurityWithSSLTest > loginWithDeprecatedSSLOptions

Root Cause: When JmxManagerBindAddress is not configured (empty string), ManagementAgent was setting pulse.host to an empty string:
System.setProperty(PULSE_HOST_PROP, "" + config.getJmxManagerBindAddress());

An empty host in the JMX service URL (service:jmx:rmi:///jndi/rmi://:PORT/jmxrmi) causes the JRE to resolve the host via InetAddress.getLocalHost(). On Linux, this returns the container's bridge IP address (e.g. 172.17.0.2) rather than 127.0.0.1.

The embedded trusted.keystore certificate has CN=localhost and a single SAN of IPAddress:127.0.0.1. When Pulse attempts the JMX-over-SSL connection to 172.17.0.2, the SSL handshake fails because that IP is not covered by the certificate.

This issue does not reproduce on macOS, where InetAddress.getLocalHost() typically returns 127.0.0.1.

Solution

In ManagementAgent.java, fall back to "localhost" when JmxManagerBindAddress is empty:
String jmxBindAddress = config.getJmxManagerBindAddress();
System.setProperty(PULSE_HOST_PROP,
jmxBindAddress.isEmpty() ? "localhost" : jmxBindAddress);

localhost resolves to 127.0.0.1, which matches the certificate's SAN, so the SSL handshake succeeds.

Testing

• Both tests pass locally (27.7s total, 0 failures)
• Code compiles and passes tests

Impact

• Eliminates test failure in CI
• Improves test reliability and developer experience

For all changes, please confirm:

• Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
• Has your PR been rebased against the latest commit within the target branch (typically develop)?
• Is your initial contribution a single, squashed commit?
• Does gradlew build run cleanly?
• Have you written or updated unit tests to verify your changes?
• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?