Adding regional EOC targets in 45_carbonprice/functionalForm

[tabeado]

Purpose of this PR

This PR is to provide an overview of the ongoing implementation of regional EOC targets in 45_carbonprice/functionalForm
The approach is described in issue 660

Type of change

Parts concerned

• ☑️ GAMS Code
• ☑️ R-scripts
• ☑️ Documentation (GAMS incode documentation, comments, tutorials)
• ◻️ Input data / CES parameters
• ◻️ Tests, CI/CD (continuous integration/deployment)
• ☑️ Configuration (switches in main.gms, default.cfg, and scenario_config*.csv files)
• ◻️ Other (please give a description)

Impact

• ◻️ Bug fix
• ◻️ Refactoring
• ☑️ New feature
• ◻️ Change of parameter values or input data (including CES parameters)
• ◻️ Minor change (default scenarios show only small differences)
• ◻️ Fundamental change of results of default scenarios

Checklist

Do not delete any line. Leave unfinished elements unchecked so others know how far along you are.
In the end all checkboxes must be ticked before you can merge.

• I executed the automated model tests (make test) after my final commit and all tests pass (FAIL 0)
• I adjusted the reporting in remind2 if and where it was needed
• I adjusted the madrat packages (mrremind and other packages involved) for input data generation if and where it was needed
• My code follows the coding etiquette
• I explained my changes within the PR, particularly in hard-to-understand areas
• I checked that the in-code documentation is up-to-date
• I adjusted forbiddenColumnNames in readCheckScenarioConfig.R in case the PR leads to deprecated switches
• I updated the CHANGELOG.md correctly (added, changed, fixed, removed, input data/calibration)

Further information (optional)

• Runs with these changes are here: /p/tmp/tabeado/Equity/EOC_2509/remind
• Comparison of results (what changes by this PR?):

[LaviniaBaumstark]

why 44?

[tabeado]

This is just an intermediate solution. 44 is a variation of 4. I think it would be good to think about a new logic for cm_iterative_target_adj in general. I also put that as a comment in the issue!