Feature/coupled maximumCap

[ciaradunks]

Fix #Issue

Changes proposed in this pull request:

• Introduce new parameter MaximumAddCap (where MaximumAddCap=MaximumCap-InstalledCap) in C0.process_maximum_cap_constraint
• Deactivate optimization when MaximumCap<=InstalledCap in C0.process_maximum_cap_constraint
• Fix MaximumCap definition in RTD and include definition for MaximumAddCap
• Replace usage of MaximumCap in D1 with MaximumAddCap calculated in C0

The following steps were realized, as well (if applies):

• [x] Use in-line comments to explain your code
• :x: Write docstrings to your code (example docstring)
• [x] For new functionalities: Explain in readthedocs
• :x: Write test(s) for your new patch of code (pytests, assertion debug messages)
• [x] Update the CHANGELOG.md
• [x] Apply black (black . --exclude docs/)
• [x] Check if benchmark tests pass locally (EXECUTE_TESTS_ON=master pytest)

_{For more information on how to contribute check the CONTRIBUTING.md.}

[ciaradunks]

@smartie2076 after making the suggested changes and running the tests, KeyError: 'maximumAddCap' is returned from D1.transformer_constant_efficiency_optimize(), for instance. Do you have an idea of why this is happening?

[smartie2076]

Yes, I do! It is the same thing that was the case in the other PR: The input files for the D0and D1tests are json files: tests/test_data/inputs_for_D0/mvs_config.json and tests/test_data/inputs_for_D1/mvs_config.json. You need to add the new parameter there as well... :/