Geological Storage improvements: Near term bounds 2035 and default costs now at 20$/tCO2

[amerfort]

Purpose of this PR

This PR adjusts the geological injection assumptions in our default scenarios in the following way:

1. default cost assumptions are now set to high, i.e. 20$/tCO2 (previously it was med 15 $/tCO2), as new research clearly shows that our current estimates are too low. We will continue to update the number, once consolidated data from the systematic reviews are available.
   Consequences: In PkBudg750 scenarios, global 2050 geological storage comes down from 6 to 5 GtCCS/yr (in line with my paper in preparation). In NPi runs, this brings down total geological storage from 600 MtCO2/yr to 400MtCO2/yr in EUR.
2. Near term limit for 2035 is now set to 2.5* 2030 bounds. This corresponds to a growth rate of 20%. Unconstrained growth lead to almost 10 fold increases and we now are more realistic. Regions without project announcements (REF and IND) start with 10 MtCO2/yr injection as upper limit in 2035.
   Consequences PkBudg750 scenarios Carbon Prices increase from 600 to 700 $/tCO2 in 2050. More realistic near-term upscaling.

Furthermore I clean up some outdated ccs constraints and add an explanation of why we omit leakage from the geological reservoir to the documentation.

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)

• Runs with these changes are here:
  `/p/tmp/amerfort/remind_documentation
  Comparison for SSP2PkBudg750 scenarios are here:
  /p/tmp/amerfort/remind_documentation/compScen-Bounds-HighCostspkBudg750-2026-06-08_11.20.52-H12.pdf

`* Comparison of results (what changes by this PR?):

See Consequences in the PR description.

[tabeado]

thank you so much for the great work!