Simplify config instantiation

[surajpaib]

Description

This PR simplifies the instantiation of a configuration by refactoring the existing code and making it more user-friendly. Monai bundle scripts are avoided and configuration parsers are used to separate from monai's structure and error-handling

Related Issue

N/A

Type of Change

• 📚 Examples / docs / tutorials / dependencies update
• 🔧 Bug fix (non-breaking change which fixes an issue)
• 🥂 Improvement (non-breaking change which improves an existing feature)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 🔐 Security fix

Checklist

• I've read the CODE_OF_CONDUCT.md document.
• I've read the CONTRIBUTING.md guide.
• I've updated the code style using make codestyle.
• I've written tests for all new methods and classes that I created.
• I've written the docstring in Google format for all the methods and classes that I used.

[ibro45]

Awesome, thank you! Can we just not use assert, and instead raise errors?

Btw, from PL 2.0, Trainer has not .tune() method, and instead you'd have to use the Tuner class. We'll have to modify the code for that but that can be a separate PR.

[surajpaib]

Awesome, thank you! Can we just not use assert, and instead raise errors?

Assert would also raise an error, right? Do we want to have specific error codes?

[ibro45]

Just style concerns, i think asserts are usually for debugging and testing purposes

[surajpaib]

Got it, will make the edit!

[ibro45]

Thanks! Btw how do the error messages look like now, is it better or do we still have to figure that out?

[surajpaib]

Thanks! Btw how do the error messages look like now, is it better or do we still have to figure that out?

This fixes it. Those error messages were thrown because we not only instantiated our config, but also called it through monai config.

Now these two are de-coupled