Move tax curve calculation to mrremind

[simonkrogmann]

Purpose of this PR

I moved the tax curve calculation from GAMS to mrremind (see pik-piam/mrremind#845). The subsidy calculation will be left for another PR. This changes behavior for cm_fetaxscen = 5 because some of the previous behavior was unintended. (Treating 0s in the rollback data as NA, confirmed with @nicobauer). Otherwise I confirmed that the taxes computed are exactly the same up to rounding differences.

I will run remind with these changes.

I removed an unused alias as well.

Type of change

Indicate the items relevant for your PR by replacing ◻️ with ☑️.
Do not delete any lines. This makes it easier to understand which areas are affected by your changes and which are not.

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)

[LaviniaBaumstark]

this required new input data, rigth?

[LaviniaBaumstark]

why should this not be part of teh switches documentation?

[simonkrogmann]

I moved the switch from using parameter to $setGlobal because parameters don't work as compile-time switches necessary for the datainput. Is there a better way for documenting setGlobal?

[LaviniaBaumstark]

starting with *' instead of *** would add this part to the automated model documentation