Track incentives

[gschivley]

Description

What type of PR is this? (check all applicable)

• [ X] Feature
• Bug Fix
• Documentation Update
• Code Refactor
• Performance Improvements

Related Tickets & Documents

Addresses #874

Checklist

• [X ] Code changes are sufficiently documented; i.e. new functions contain docstrings and .md files under /docs/src have been updated if necessary.
• [X ] The latest changes on the target branch have been incorporated, so that any conflicts are taken care of before merging. This can be accomplished either by merging in the target branch (e.g. 'git merge develop') or by rebasing on top of the target branch (e.g. 'git rebase develop'). Please do not hesitate to reach out to the GenX development team if you need help with this.
• [ X] Code has been tested to ensure all functionality works as intended.
• [X ] CHANGELOG.md has been updated (if this is a 'notable' change).
• [ X] I consent to the release of this PR's code under the GNU General Public license.

How this can be tested

Added an example case with investment and production incentives, although the production incentives are only for energy. Might want to add a CCS resource and a CO₂ production incentive to the test.

Outputs now include investment/production incentives in the costs file and their own results files. Names should be checked for all outputs.

Post-approval checklist for GenX core developers

After the PR is approved

• Check that the latest changes on the target branch are incorporated, either via merge or rebase
• Remember to squash and merge if incorporating into develop

[gschivley]

@lbonaldo and @sambuddhac, please take a careful look at this. It's passing tests but I relied heavily on copilot for all code changes. We might still want to make some changes to names in new files.

[sambuddhac]

I will be doing a thorough review and test of it today. Thanks @gschivley