feat(config): add explicit validation for required configuration fields

[Sourish-07]

What changed

This PR adds explicit validation to the Config class to surface missing required configuration fields early, with clear error messages.

Why

Currently, missing core fields such as provider_uri or region can lead to unclear runtime errors later in the execution flow. This change fails fast and makes misconfiguration easier to diagnose.

What’s included

• A new Config.validate() method that checks required fields
• A focused unit test validating the behavior for missing provider_uri

Notes

Some tests depend on optional development packages (e.g. tqdm), so local test collection may fail on a minimal setup. CI should be used to verify test results.

[Sourish-07]

@microsoft-github-policy-service agree

[SunsetWolf]

Hi, @Sourish-07 , Thanks for the contribution! The CI checks are currently failing due to code formatting issues.
Could you please adjust the formatting and update the PR so that all CI checks pass?

[Sourish-07]

Hi, I’ve rebased the branch onto the latest upstream main, cleaned up the formatting issues, and updated the validation logic to respect skip_register. The changes are now pushed to the PR. Please let me know if there are any other changes required.

[Sourish-07]

Hi @SunsetWolf, CI is passing and the requested changes are in. Could you take a quick look and merge if it looks good?
Thanks you.