Feature/config validation

[kris927b]

I just finished implementing configuration validation.

Here's a summary of what I did:

• I added a command-line flag to help you validate your configuration file. When you use it, I'll load and check the pipeline configuration file you specify and then exit.
• I've put in place schema validation and new logical validation rules for each step of your pipeline configuration.
• These logical checks make sure that parameter values are within acceptable ranges and that there are no conflicting settings.
• Now, when I load your pipeline configuration, I'll automatically perform these validation checks after parsing the file.
• I've added a specific error type for configuration issues to make reporting clearer.
• I also included comprehensive unit tests to cover all the new validation logic, ensuring that both valid and invalid configurations are handled correctly.

This enhancement should help you catch configuration errors early, which will make your data processing pipeline more robust and easier to use.