feat: add support for versioned constants in Orchestrator

[byteZorvin]

Pull Request type

Please add the labels corresponding to the type of changes your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build-related changes
• Documentation content changes
• Testing
• Other (please describe):

What is the current behavior?

• Orchestrator does not have support for custom version constants

Resolves: #NA

What is the new behavior?

• Orchestrator has custom version constant support

Does this introduce a breaking change?

Other information

[Mohiiit]

instead of taking the path and then converting the yaml/json file to the versionconstants, we can do something like this:

fn parse_constants(path: &str) -> Result<VersionedConstants, String> {
    std::fs::read_to_string(path)
        .map_err(|e| e.to_string())
        .and_then(|content| {
            serde_json::from_str::<VersionedConstants>(&content)
                .map_err(|e| e.to_string())
        })
}

#[derive(Parser, Debug)]
pub struct Args {
    #[arg(
        env = "MADARA_ORCHESTRATOR_VERSIONED_CONSTANTS_PATH",
        long,
        value_parser = parse_constants
    )]
    pub versioned_constants: Option<VersionedConstants>,
}

this way we won't have to add versioned_constants in the ConfigParam and it would be part of the snos_config only and can be used directly then