update submodule

[Emre-Yorat89]

Closes # (if applicable).

Changes proposed in this Pull Request

Checklist

• I consent to the release of this PR's code under the GPLv3 license and non-code contributions under CC0-1.0 and CC-BY-4.0.
• I tested my contribution locally and it seems to work fine.
• Code and workflow changes are sufficiently documented.
• Newly introduced dependencies are added to the main environment at PyPSA-Earth repository
• Changes in configuration options are added in all of config.default.yaml and config.tutorial.yaml.
• Add a test config or line additions to test/ (note tests are changing the config.tutorial.yaml)
• Changes in configuration options are also documented in doc/configtables/*.csv and line references are adjusted in doc/configuration.rst and doc/tutorial.rst.
• A note for the release notes doc/release_notes.rst is amended in the format of previous release notes, including reference to the requested PR.

[davide-f]

Great @Emre-Yorat89 :D
Many thanks for the contribution, unfortunately it seems there is still a problem with the CI.

The problem relies on the merge event that has lead to significant changes in pypsa-earth and the revision of the config implementation.
Now configs are incrementally changed starting from a default config file and then changes are added subsequently.

For example, if you look at config.tutorial.yaml, the content has significantly changed.

Updating the repo to the latest change is a bit more challenging, it may be easier to create a custom environment file instead.
Would you like to open a new PR where we add a folder "envs" and inside we place a new environment file that is the same as the one we currently use for pypsa-distribution:
https://github.com/pypsa-meets-earth/pypsa-earth/blob/c1d4b993dc52d1f22a46efab983bcef5289afb95/envs/environment.yaml

but we add:

• ramp
• the rasterio fix here: https://github.com/pypsa-meets-earth/pypsa-earth/blob/489ff8f9fb8b35cd4730910a23411da57ebd28e6/envs/environment.yaml#L59

@Margherita-Capitani has proposed also a similar solution :)

Contestually, it would be great to revise the installation guide of:

• README.md: this shall revise the section of conda env create to link to the newly created file envs/environment.yaml
• doc/installation.rst: similarly to above, it shall be revised accordingly