Updated TDR to fix PeriodMap.csv error (Issue 250)

[dharik13]

Description

• Updated time_domain_reduction.jl to fix error in the assignment of representative period, which result in a d Rep_Period key not being equal to the period_index when the period that actually a representative period.
• Each representative period should be used to represent the period of the year (column Period_Index of Period Map) corresponding to its Rep_Period key. That was not happening before due to a bug in Step 4 of the TDR procedure.

• Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes issue \

Please tag any associated issues here using the format Fixes #<issue number>. If there is no associated issue, please type No associated issue.

Type of change

Please delete options that are not relevant.

• [X ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

• Tested on SmallNewEngland system, OneZone and ThreeZone_Gurobi for different TDR settings (extremeperiods =0 or 1, clusterfuelprices =0 or 1)

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

• [X ] Example_Systems/SmallNewEngland/OneZone
• [ X] Example_Systems/SmallNewEngland/ThreeZones_Gurobi

Test Configuration:

• OS: Windows
• Solver: HiGHs
• Julia version: 1.10.0
• Solver version: 1.7.2

Checklist:

• [X ] My code follows the style guidelines of this project
• [X ] I have performed a self-review of my code
• [X] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [X ] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes
• [X ] I have run tests with my code to avoid compatibility issues
• [X ] Any dependent changes have been merged and published in downstream modules