Add support for configure using TOML files

[savente93]

Issue addressed

Fixes #376

Explanation

Very simple implementation, because almost everything is done using dictionaries all that was needed was just swap the yaml functionality for the toml. (doc updates to come)

Checklist

• Updated tests or added new tests
• Branch is up to date with main
• Tests & pre-commit hooks pass
• Updated documentation if needed
• Updated changelog.rst if needed

Additional Notes (optional)

Add any additional notes or information that may be helpful.

[savente93]

Since Toml doesn't support any type of None value, I also took the liberty to Fix #152

[DirkEilander]

Thanks for this this PR @savente93! I noticed that the PR does more than just fixing #376, which requests toml support for model configuration files in the Model.read_config / write_config methods. This PR also adds toml support for HydroMT data catalog and configuration files. We should have a discussion with the team/users if this is indeed wanted.

My initial thoughts:
In general I can imagine that different file formats will only confuse users.
For the HydroMT configuration file I see a benefit though. If the model configuration is in toml (like for most PMT HYD models) it might actually be convenient for users if the HydroMT configuration can also be done in toml.
For the HydroMT data catalog file I think we should stick to toml as it has many more "layers" for which I think toml is not very readable. Let's discuss at the next stand-up how to proceed with this.

What do you think @hboisgon @alimeshgi @B-Dalmijn @Tjalling-dejong ?

[savente93]

right, that's true. The part of the catalog being in TOML was from when I still misunderstood the objective. I still think it's a nice feature though, especially given the recommendations from DSC. Do note that I'm not suggesting we move everything to toml, this is simply support for it, so it would enable users to have all their config files in toml if they'd like. But as you say, let's indeed discuss in the next standup.

[alimeshgi]

I agree that using different file formats can potentially confuse users. Consistency in file formats often helps maintain simplicity and ease of use. Yes, let's discuss it in the next stand-up.

[savente93]

Converted to draft until we can reach a consensus on #452

[DirkEilander]

LGTM!