Commands return partial or incomplete data with response aggregation

[Muhammad-awawdi-amazon]

Describe the bug

Commands that aggregate responses from multiple nodes (e.g., INFO routed to allNodes) may return partial or incomplete data.
This behavior is observed with the ResponsePolicy::Special policy and is not exclusive to the allNodes route.

Expected Behavior

Commands with response aggregation should handle errors gracefully.
If responses from some nodes are missing:

• Return an error indicating incomplete results.

• Alternatively, provide a result map with successful results and errors.

Current Behavior

When routed to allNodes, INFO may return incomplete data due to network or node conditions.

Reproduction Steps

const client = await GlideClusterClient.createClient({
    addresses: cluster.getAddresses(),
    protocolVersion: ProtocolVersion.RESP3,
    route: "allNodes",
});

try {
    const result = await client.info();
    console.log(result); // May show partial data or an empty map
} finally {
    client.close();
}

Possible Solution

Implement a result map that:
Includes results from successful nodes.
Captures errors or failures for nodes that do not respond.

Additional Information/Context

No response

Client version used

1.2.1

Engine type and version

Valkey 8.0.1

OS

Ubuntu

Language

TypeScript

Language Version

5.2.2

Cluster information

Cluster Information:

Cluster with 3 primaries and 4 replicas.
Commands routed to all nodes or specific nodes for response aggregation.

Logs

No response

Other information

No response

[Muhammad-awawdi-amazon]

Related to issue #2837 with the flaky test, was solved with adding request timeout of 3 seconds when creating the client