feat: Make env using custom config file path in kwargs

[kostialjn]

Specify custom config.py file using kwargs. Related to issue #738

# Load env using config.py in root directory
env = grid2op.make(root_path)

# Load env using custom config.py anywhere else
env = grid2op.make(root_path, _config_path="path/to/custom/config.py")

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[BDonnot]

Hello,

Is this PR still relevant or have you find a better solution ?

[kostialjn]

@BDonnot

What we did was :

• Create a fake empty config at env folder root

# Content of config.py
config = {}

• Create several custom config.py (config1.py, config2.py, etc)
• Import the one needed and load environment with it by assigning them through kwargs:

from .config1 import config
env = grid2op.make(..., **config)

The only problem was that some kwargs names are incompatible with some config.py fieds see issue #740 for instance

[BDonnot]

Get it 😊

This will be fixed in next release.

I will double check every config names to match the kwargs names.

But in the same time and before the release, I wanted to merge anything that could be merged.

This is why I wanted to check whether this makes sense to merge this PR.