784 bug capres flag for transmission lines does not appear to do anything

[lbonaldo]

Description

Addresses #784 by updating the documentation for the Network.csv file and removing the CapRes_* column from examples and tests. It should now be clearer that users should use the following:

• CapResExcl_* != 0: enables the contribution of the transmission line to the Capacity Reserve Margin (CRM).
• CapResExcl_* == -1: indicates that the designated direction of the transmission line is inbound to the LDA.
• CapResExcl_* == 1: direction of the transmission line is outbound from the LDA.

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

• Documentation Update

Related Tickets & Documents

Addresses #784.

Checklist

• Code changes are sufficiently documented; i.e. new functions contain docstrings and .md files under /docs/src have been updated if necessary.
• 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.
• Code has been tested to ensure all functionality works as intended.
• CHANGELOG.md has been updated (if this is a 'notable' change).
• I consent to the release of this PR's code under the GNU General Public license.

How this can be tested

Example case 7_three_zones_w_colocated_VRE_storage.

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

[lbonaldo]

@gschivley

[gmantegna]

Looks good to me!