Can we improve the configuration files to be easier to read and write?

Currently, the configuration files are designed as optuna-compatible functions, but this adds boilerplate (such as f"_{name}".) And maybe confusing and hard to understand.

It would help with clarity if we can have a different format that still supports the features of the optuna suggestions and types, but is easier to read and write.

This may also make it easier to set random states for reproducibility #53