Bugfix: windoff capacity factor was too low

[lecfab]

Purpose of this PR

VRE capacity factors are interpolated between historical values (p_aux_capacityFactorHistOverREMIND) and a default factor 1. For offshore however, p_aux_capacityFactorHistOverREMIND was not set in some regions, therefore taking the value zero and leading to very low capacity factors in the near-term:

# /p/projects/remind/modeltests/remind/output/SSP2-PkBudg650-AMT_2024-09-28_01.49.00/
# dumpgdx fulldata.gdx vm_capFac 202.*,windoff,l,
# 2020
2020  LAM  windoff  L  0.25
2020  OAS  windoff  L  0.25
2020  SSA  windoff  L  0.25
2020  EUR  windoff  L  0.772409095660856
2020  NEU  windoff  L  0.25
2020  MEA  windoff  L  0.25
2020  REF  windoff  L  0.25
2020  CAZ  windoff  L  0.25
2020  CHA  windoff  L  0.59905006244186
2020  IND  windoff  L  0.25
2020  JPN  windoff  L  0.25
2020  USA  windoff  L  0.25
# 2025
2025  LAM  windoff  L  0.5
2025  OAS  windoff  L  0.5
2025  SSA  windoff  L  0.5
2025  EUR  windoff  L  0.848272730440571
2025  NEU  windoff  L  0.5
2025  MEA  windoff  L  0.5
2025  REF  windoff  L  0.5
2025  CAZ  windoff  L  0.5
2025  CHA  windoff  L  0.732700041627907
2025  IND  windoff  L  0.5
2025  JPN  windoff  L  0.5
2025  USA  windoff  L  0.5

This PR puts p_aux_capacityFactorHistOverREMIND to 1 by default.

Type of change

(Make sure to delete from the Type-of-change list the items not relevant to your PR)

• Bug fix
• Refactoring
• New feature
• Minor change (default scenarios show only small differences)
• Fundamental change
• This change requires a documentation update

Checklist:

• My code follows the coding etiquette
• I performed a self-review of my own code
• 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 the reporting in remind2 where it was needed
• I adjusted forbiddenColumnNames in readCheckScenarioConfig.R in case the PR leads to deprecated switches
• All automated model tests pass (FAIL 0 in the output of make test)
• The changelog CHANGELOG.md has been updated correctly

Further information (optional):

• Test runs are here:
• Comparison of results (what changes by this PR?):