Add oem2orm to poetry

[MaGering]

This rule upload_results_to_oep needs the package oem2orm. So far it has been listed in the extra requirements of poetry (cf. here).

However this info is not given anywhere in the documentation. But more severe is that the prompt poetry install -E upload_results_to_oep leads to No dependencies to install or update.. It can not be installed via the extra requirements.

That's why with this PR oem2orm is added to the main dependencies.

To be tested with:

snakemake -j1 results/2050-80-el_eff/b3_results/metadata
snakemake -j1 results/2050-80-gas_moreCH4/b3_results/metadata
snakemake -j1 results/2050-95-el_eff/b3_results/metadata
snakemake -j1 results/2050-95-gas_moreCH4/b3_results/metadata
snakemake -j1 results/2050-100-el_eff/b3_results/metadata
snakemake -j1 results/2050-100-gas_moreCH4/b3_results/metadata

[MaGering]

Outdated: Again checks not working due to problem described in my comment here. Hence this PR should be merged after #336.

Checks pass as of the state of commit 911f404.

[Stefanie08]

Outdated: I have tested the dev branch with a new created environment. The processing of the rule upload_results_to_oep stops at the input of the OEP-username. This goes for all scenarios.

After merging the branch fix/add_oem2orm_pckg into the branch features/update_tabular, merge conflicts are raised. Mainly in the poetry.lock file and one in the pyproject.toml.
The process to achieve the same outcome as the one in the dev branch, the complete poetry.lock file from the merged branches needs to be replaced with the poetry.lock file of the branch features/update_tabular. After resolving the merge conflicts the tests can be run.
Before that I tried to manually fix the merge conflicts, executed poetry lock and poetry install to update the packages. This approach leads to an error message of the following (for windows):

TypeError: Flow._init_() got an unexpected keyword argument 'gas-heat_central-B'

[Stefanie08]

Changes work as expected