Core: Add support for sending multi-slot JSON.MSET and JSON.MGET commands

[barshaul]

Description

This PR adds support for handling JSON.MSET and JSON.MGET commands with multi-slot keys, expanding the argument patterns that are currently supported. Prior to this PR, the system only supported two argument patterns for MGET and MSET: keys only, and key value pairs. This update introduces support for two additional patterns:

1. Keys and Path: Relevant for the JSON.MGET command, which follows the format JSON.MGET key1 key2 key3 path.
2. Key Path Value Triples: Relevant for the JSON.MSET command, which follows the format JSON.MSET key1 path1 value1 key2 path2 value2.

All patterns are now being represented with the MultiSlotArgPattern enum.

Multi-Slot Command Handling:

There are two main parts in handling multi-slot commands:

1. Command Splitting:

   • The multi_shard function is responsible for splitting commands into sub-commands based on the slots each key belongs to. This PR enables the correct splitting of JSON.MGET and JSON.MSET commands based on the newly added argument patterns (KeysAndPath and KeyPathValueTriples).

2. Response Aggregation:

   • There are two main response policies for aggregating responses from sub-commands:
     • Array Combination (default for commands like MGET and JSON.MGET): Combines all sub-command responses into a single array, maintaining the order of commands in the original request.
     • AllSucceeded (used for commands like MSET and JSON.MSET): Returns OK if all sub-commands succeed; otherwise, returns the first encountered error.

Although MSET and JSON.MSET currently don’t use combined array responses in Glide, this PR adds support for combining results into a single array for these commands too. This enhancement prepares for a future feature where responses can return an array of OK and Error results, allowing the operation to continue without failing entirely if a request for a single slot fails.

This extension enables enhanced multi-slot handling for JSON.MGET and JSON.MSET, improving the client's ability to manage complex, multi-slot commands and aggregate responses accurately.

Issue link

This Pull Request is linked to issue (URL): closes #2455

Checklist

Before submitting the PR make sure the following are checked:

• [ X] This Pull Request is related to one issue.
• [X ] Commit message has a detailed description of what changed and why.
• [X ] Tests are added or updated.
• [ X] CHANGELOG.md and documentation files are updated.
• [ X] Destination branch is correct - main or release
• [ X] Commits will be squashed upon merging.

[Yury-Fridlyand]

Thanks

[eifrah-aws]

So the idea is to cover all options here? e.g. if I look at HSET, which has HSET KEY field value [field value..] are we going to create a new enumerator here?

[barshaul]

HSET has a single key, so it wont be a multi-slot command. But, in general, yes - if there is going to be a command with a new pattern that we can support it in a multi-slot option, we will add it here

[Yury-Fridlyand]

LGTM.
Can't post an approval, because I can't assess the rust code part.