[irm-codebase]

Fixes #29

Summary of changes in this pull request

• Optional user provided file for annual generation.
• Users can choose between EIA or their own file via the configuration.
• The output statistics has been expanded to include all EIA statistics for the provided spatial extent (not just the requested years). This makes it possible to modify this file and pass it as an input (with no DAG breakage) in cases where the user's workflow wants to do fancy imputation, adjustments or complete replacement of the data.

If GLOFAS discharge makes it in, this input might become irrelevant based on this comment: #25 (comment) (but that's for later).

Reviewer checklist

• There are no pip dependencies in the module's environment files (workflow/envs/).
• All rules use pathvars (e.g., <results>) in their inputs and outputs.
• The integration test-suite is successful, including:
  • pre-commit.ci tests pass.
  • tests pass for all relevant OS configurations (linux, osx, windows).
• Module documentation is up-to-date, including:
  • INTERFACE.yaml mentions all relevant pathvars and wildcards.
  • README.md describes how to use the module and has the necessary citations.

[irm-codebase]

@cdgaete, @brynpickering:
Here is a relatively simple implementation of my idea in #29 (comment)

It should allow you to impute any year in the ERA5 data, with no need for download or cleaning code on the PyPSA-Eur side (just imputation), and it covers all 3 cases mentioned in the original issue.

LMKWYT.