Add support for XDELEX and XACKDEL, and expand options for XADD and XTRIM

[viktoriya-kutsarova]

This change introduces the Support XDELEX, XACKEX and extend XADD and XTRIM options feature as part of the features provided by the spring-data-redis project. Closes #3232.

As part of the change the following commands would be made available:

• XDELEX - deletes one or multiple entries from the stream at the specified key. XDELEX is an extension of the Redis Streams XDEL command that provides more control over how message entries are deleted concerning consumer groups.
• XACKDEL - acknowledges and conditionally deletes one or multiple entries (messages) for a stream consumer group at the specified key. XACKDEL combines the functionality of XACK and XDEL in Redis Streams. It acknowledges the specified entry IDs in the given consumer group and simultaneously attempts to delete the corresponding entries from the stream.

As part of the change the following command options would be made available for XADD and XTRIM:

• KEEPREF | DELREF | ACKED - Specifies how to handle consumer group references when trimming. Available since Redis 8.2. If no option is specified, KEEPREF is used by default. Unlike the XDELEX and XACKDEL commands where one of these options is required, here they are optional to maintain backward compatibility:
• =: Exact trimming (default) - trims to the exact threshold
• LIMIT count - Limits the number of entries to examine during trimming. Available since Redis 6.2.0. When not specified, Redis uses a default value of 100 * the number of entries in a macro node. Specifying 0 disables the limiting mechanism entirely.

The new commands are available as part of the following interfaces:

• RedisStreamCommands / ReactiveStreamCommands
• StreamOperations / ReactiveStreamOperations / BoundStreamOperations
• StringRedisConnection
• New enum StreamDeletionPolicy and StreamEntryDeletionResult inside RedisStreamCommands

This feature is available starting from Redis OSS version 8.2.x and later

---

• You have read the Spring Data contribution guidelines.
• You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.
• You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

---

Closes #3232

[onobc]

Great work @viktoriya-kutsarova !

Thank you for the contribution. Closing in favor of ab12ddd