update shared_resources "base" to not retrigger renewable profiles

[p-glaum]

Makes that with shared_resources=base, the previous behavior is recovered and every rule starting from add_electricity is not shared anymore, but the renewable profiles are shared.

Changes proposed in this Pull Request

Checklist

• I tested my contribution locally and it works as intended.
• Code and workflow changes are sufficiently documented.
• Changed dependencies are added to envs/environment.yaml.
• Changes in configuration options are added in config/config.default.yaml.
• Changes in configuration options are documented in doc/configtables/*.csv.
• Sources of newly added data are documented in doc/data_sources.rst.
• A release note doc/release_notes.rst is added.

[lindnemi]

why is the or is_shared necessary? Looks like it could be omitted

[p-glaum]

In my opinion, this is necessary here.
Because for the first is_shared, in the previous behaviour, you had neither a relevant_wildcard nor a shared_rule to make it shared. However, with the new structure, this would always be False for the profiles, meaning that they are never shared in the end.
This is why I added shared_files, and if any of those is in the file name, then the resource is always shared.

[fneum]

I would like to test this. Do you have a configfile/s to run to validate the intended behaviour?

[p-glaum]

I just had two different scenarios "A", "B" like

run:
  prefix: 'test_shared_resources'
  name: 
    - A
    - B
  scenarios:
    enable: true
    file: config/scenarios.yaml
  disable_progressbar: true
  shared_resources:
    policy: base
    exclude: []
  shared_cutouts: true

with the scenario.yaml

A:
electricity:
  renewable_carriers: [solar, onwind]

B:
electricity:
  renewable_carriers: [solar, offwind-dc]