Add RediSearch Dialect Version Configuration Option

[uglide]

In the current implementation of the client, users are required to specify the RediSearch dialect version for every FT.SEARCH or FT.AGGREGATE command. This repetitive configuration process might be prone to errors and can lead to inconsistency issues across different parts of a project where different dialect versions might be unintentionally used.

In order to make our client more user-friendly and maintain consistency throughout the usage, we need to provide a configuration option that allows users to set the RediSearch dialect version at the connection level. This will ensure the specified version is used across all FT.SEARCH and FT.AGGREGATE commands, removing the need to set it individually each time.

Acceptance Criteria:

• A new configuration option should be added to the client that allows users to specify the RediSearch dialect version at the connection level.
• This configuration option should be optional. If it is not specified, the client should fall back to the current behavior.
• If the configuration option is set, all FT.SEARCH, FT.AGGREGATE, FT.EXPLAIN, FT.EXPLAINCLI, and FT.SPELLCHECK commands should use the specified RediSearch dialect version by default.

[leibale]

1. This should be a server-side feature (config for default dialect).
2. If you want to make sure you are using the same dialect across all FT.SEARCH you can create a "wrapper function":

   function search(idx, query, options) {
   options ??= {};
   options.DIALECT ??= DEFAULT_DIALECT;
   return client.ft.search(idx, query, options);
   }

[uglide]

@leibale At the moment, there is no support for it on server side in the cloud. That's why adding it on the client side is easier as a first step.

[uglide]

@leibale btw, we need it for multiple commands and it's not developer-friendly to have 6 wrappers around FT.SEARCH, FT.AGGREGATE, FT.EXPLAIN, FT.EXPLAINCLI, and FT.SPELLCHECK commands to set dialect version.