Constrain Snakefile rule build_renewable_profiles with wildcard_constraint

[euronion]

• Introduce a wildcard_constraint to limit build_renewable_profiles to certain technologies.
• Remove potential ambuitiy for resources/profile_hydro.nc
• Remove optional inclusion of build_hydro_profile: Unnecessary, as rule is only executed, if add_electricity wants it.

Side effect:

• Easier to understand snakemake errors when trying to run with an unsupported technology :

# before PR
$ snakemake -call -n resources/profile_hello.nc
Building DAG of jobs...
InputFunctionException in line 185 of .../pypsa-eur/Snakefile:
Error:
  KeyError: 'hello'
Wildcards:
  technology=hello
Traceback:
  File ".../Snakefile", line 191, in <lambda>

# after PR
$ snakemake -call -n resources/profile_hello.nc
Building DAG of jobs...
MissingRuleException:
No rule to produce resources/profile_hello.nc (if you use input functions make sure that they don't raise unexpected exceptions).

Checklist

• I tested my contribution locally and it seems to work fine.
• Code and workflow changes are sufficiently documented.
• Newly introduced dependencies are added to envs/environment.yaml and envs/environment.docs.yaml.
• Changes in configuration options are added in all of config.default.yaml, config.tutorial.yaml, and test/config.test1.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.

[euronion]

Ok, CI failed because the test config.yaml did not contain the hydro key. The new push should fix that.

The aim was to make not the rule optional, but present a more deterministic set of rules which is not based on the existance of config values.

Output in case build_hydro_profiles is called now without an hydro key being defined in the config:

$ snakemake -call -n resources/profile_hydro.nc
Building DAG of jobs...
MissingInputException in line 208 of .../Snakefile:
Missing input files for rule build_hydro_profile:
config['renewable']['hydro']['cutout'] not configured

[fneum]

What about a ruleorder?

https://snakemake.readthedocs.io/en/stable/snakefiles/rules.html#handling-ambiguous-rules

[euronion]

Rule order makes sense IMHO if the rules are ambigious. In our case the rules don't need to be ambigious, so I'd prefer to use that route rather than keeping them ambigiuous.