Add KeyValue and EvaluationContext args to compare

[Richardds]

Problem Statement:
The current compare command in Redis RIOT does not support specifying key/value processing arguments, such as --key-proc, when performing an on-demand comparison. This limits the ability to replicate the same key transformations that are automatically applied during the replication process (e.g., prefixing keys with --key-proc "yourprefix:#{key}" argument).

While the automatic comparison after each replicate scan cycle correctly respects these transformations, the on-demand compare command lacks the capability to apply them, which prevents users from comparing data in the same way as they would during replication.

Proposed Solution:
This PR introduces support for key/value processing arguments (e.g., --key-proc) to the on-demand compare command using the same KeyValueProcessorArgs as in replicate command. This ensures that users can apply the same transformations during ad-hoc comparisons as they can during the replication process, maintaining consistent behavior between automatic and on-demand comparisons.

Benefits:

• Feature Parity: Aligns the on-demand compare command with the automatic compare performed after each scan cycle.
• Flexibility: Enables users to run ad-hoc comparisons with the same key/value transformation options used during replication.
• Improved Workflow: Helps users verify and debug key manipulations more easily, especially for complex scenarios where keys or values are dynamically transformed during replication.

Use Case:
For example, when replicating keys and prefixing them (e.g., with --key-proc "yourprefix:#{key}" argument), users cannot currently perform an accurate on-demand comparison because the transformations are not applied in the compare command. This PR resolves that limitation by enabling key/value processing arguments in the on-demand comparison.

[jruaux]

Thank you for reporting this. I put your changes in AbstractCompareCommand to avoid code duplication between compare and replicate.

[jruaux]

🎉 This issue has been resolved in v4.1.3 (Release Notes)