Add emep base-config for reporting

[heikoklein]

Change Summary

The emep config is very long and modellers repeatedly used inconsistent versions of the base-config. Therefore, a base-config with the most common parameters is bundled with pyaerocom. The modeller only needs to adapt the base-config.

Related issue number

fixes https://github.com/metno/AeroToolsIssues/issues/2

Checklist

• Start with a draft-PR
• The PR title is a good summary of the changes
• PR is set to AeroTools and a tentative milestone
• Documentation reflects the changes where applicable
• Tests for the changes exist where applicable
• Tests pass locally
• Tests pass on CI
• At least 1 reviewer is selected
• Make PR ready to review

[codecov]

Codecov Report

Attention: Patch coverage is 93.65079% with 4 lines in your changes missing coverage. Please review.

Project coverage is 79.04%. Comparing base (1bf6fc2) to head (9365dc0).
Report is 452 commits behind head on main-dev.

Files with missing lines	Patch %	Lines
pyaerocom/aeroval/config/emep/reporting_base.py	93.65%	4 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##           main-dev    #1276      +/-   ##
============================================
+ Coverage     78.96%   79.04%   +0.08%     
============================================
  Files           133      135       +2     
  Lines         20599    20766     +167     
============================================
+ Hits          16265    16414     +149     
- Misses         4334     4352      +18     

Flag	Coverage Δ
unittests	79.04% <93.65%> (+0.08%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[lewisblake]

Please clean up dead code. I also wonder if we should link to the documentation in the config.

[lewisblake]

I think we should try to model "good behavior" in this config by supplying the data types that EvalSetup actually expects. So for var_order_menu, this is a tuple of strings, not a list.

[heikoklein]

The user should be able to add or remove variable in the var_order_menu before sending it to EvalSetup. This becomes unnecessarily cumbersome if it is a tuple. EvalSetup/pedantic to the cleanup/conversion to tuples.