Implement the `SAVE` Command for Data Persistence

[proXDhiya]

Develop the SAVE command to manage the configuration of the save signal for the data persistence worker. This command will allow users to specify conditions under which the dataset is automatically dumped to disk. For example, the command save 60 1000 should configure the system to dump the dataset every 60 seconds if at least 1000 keys have changed.

Requirements:

• Implement the SAVE command with the following functionalities:
  • Allow configuration in the format save <seconds> <changes>.
  • The system should automatically trigger the save signal to the worker based on this configuration.
  • If the SAVE command is called without additional arguments, it should immediately trigger a save signal to the worker.
  • If no SAVE command is not set, the RDP worker should not run to save the files automatically.

Acceptance Criteria:

• The SAVE command can configure automatic dataset dumps based on the specified conditions.
• The system triggers the save signal to the worker according to the SAVE command configuration.
• Calling SAVE without arguments triggers an immediate save signal.
• If no SAVE command is set, the worker does not attempt to save files.

Additional Notes:

• Ensure the implementation integrates seamlessly with the existing RDP worker.
• Consider edge cases, such as conflicting configurations or improper usage of the SAVE command.