C++ client incompatible with Hazelcast`5.5.0` [HZG-188]

[JackPGreen]

When testing C++ client against Hazelcast 5.5.0, the PR builder failed with:

2025-03-20T14:57:05.6591790Z INFO: [localhost]:5701 [dev] [5.5.0] [localhost]:5701 is STARTED
2025-03-20T14:57:05.6600940Z 14:57:05,659  INFO [Main] - Ping ... Pong ...
2025-03-20T14:57:05.6623500Z 20/03/2025 14:57:05.661 INFO: [0x16b44b000] hz.client_1[dev] [5.3] (Thu Mar 20 14:48:56 2025 +0000:33897ea) LifecycleService::LifecycleEvent Client (b0fdfbb9-639c-4a21-805f-30a57d39cd89) is STARTING
2025-03-20T14:57:05.6628900Z 20/03/2025 14:57:05.661 INFO: [0x16b44b000] hz.client_1[dev] [5.3] (Thu Mar 20 14:48:56 2025 +0000:33897ea) LifecycleService::LifecycleEvent STARTING
2025-03-20T14:57:05.6631030Z 20/03/2025 14:57:05.661 INFO: [0x16b44b000] hz.client_1[dev] [5.3] LifecycleService::LifecycleEvent STARTED
2025-03-20T14:57:05.6642750Z 20/03/2025 14:57:05.662 INFO: [0x16b44b000] hz.client_1[dev] [5.3] Trying to connect to Address[127.0.0.1:5701].
2025-03-20T14:57:05.6869660Z Mar 20, 2025 2:57:05 PM com.hazelcast.client.impl.protocol.task.AuthenticationMessageTask
2025-03-20T14:57:05.6871470Z INFO: [localhost]:5701 [dev] [5.5.0] Received auth from Connection[id=1, /127.0.0.1:5701->/127.0.0.1:49224, qualifier=null, endpoint=[127.0.0.1]:49224, remoteUuid=b0fdfbb9-639c-4a21-805f-30a57d39cd89, alive=true, connectionType=CPP, planeIndex=-1], successfully authenticated, clientUuid: b0fdfbb9-639c-4a21-805f-30a57d39cd89, client name: hz.client_1, client version: 5.3
2025-03-20T14:57:05.6973600Z 20/03/2025 14:57:05.697 INFO: [0x16b44b000] hz.client_1[dev] [5.3] LifecycleService::LifecycleEvent CLIENT_CONNECTED
2025-03-20T14:57:05.6978690Z 20/03/2025 14:57:05.697 INFO: [0x16b44b000] hz.client_1[dev] [5.3] Authenticated with server  Address[localhost:5701]:564429cc-b05d-4bf8-988f-04179cb22586, server version: 5.5.0, local address: Address[127.0.0.1:49224]. Connection{alive=1, connection id=1, remote endpoint=Address[localhost:5701], last_read_time=2025-03-20 14:57:05.695, last_write_time=2025-03-20 14:57:05.664, closedTime=never, connected server version=5.5.0}
2025-03-20T14:57:05.7071720Z 20/03/2025 14:57:05.706 WARNING: [0x16c053000] hz.client_1[dev] [5.3] No invocation for callId:  0. Dropping this message: ClientMessage{length=61, operation=, isRetryable=0, correlationId = 0, messageType = 0x304, flags = 0xc200, is backup aware = 0, is backup event = 0, isEvent = 1}, is_fragmented = no
2025-03-20T14:57:05.7073140Z 20/03/2025 14:57:05.706 INFO: [0x16bd0b000] hz.client_1[dev] [5.3] 
2025-03-20T14:57:05.7076280Z 
2025-03-20T14:57:05.7076570Z Members [1]  {
2025-03-20T14:57:05.7077090Z 	Member[localhost]:5701 - 564429cc-b05d-4bf8-988f-04179cb22586
2025-03-20T14:57:05.7181200Z ./scripts/test-unix.sh: line 60: 27824 Segmentation fault: 11  ${TEST_EXECUTABLE} --gtest_output="xml:CPP_Client_Test_Report.xml"
2025-03-20T14:57:05.7182730Z }
2025-03-20T14:57:05.7195620Z 
2025-03-20T14:57:05.7201530Z Mar 20, 2025 2:57:05 PM com.hazelcast.internal.server.tcp.TcpServerConnection
2025-03-20T14:57:05.7204640Z Test FAILED. Result:139

[ihsandemir]

Related to SUP-566

[JackPGreen]

We may want to consider instead running the nightly tests against a Hazelcast (platform) master/nightly build to flag upstream compatibility issues earlier.

I did something similar in #1274.

EDIT - In hindsight, this is a bad idea - it introduces external variability (and flake) into the testing process. We can catch the issue better elsewhere.