Introduce market zones

[nick-harder]

Pull Request

Related Issue

Closes #385 (if applicable)

Description

This PR introduces a mechanism to clear the market according to defined market zones while maintaining information about individual nodes. This allows for specific market zones within the energy market to be established, enabling a subsequent nodal-based market, such as redispatch, to be executed.

Market zones can be specified in the buses.csv file by associating nodes with particular zones using a zones_identifier column. This zones_identifier can then be referenced in the configuration file and utilized by the complex market clearing algorithm to create the bidding zones.

Currently, the transfer capacity between zones is calculated by summing the thermal capacities of lines between various zones. In future iterations, this will be enhanced to support the import of external transfer capacities or to calculate them based on the market clearing results.

Changes Proposed

• Added zone_id to the configuration file, complex market clearing, and buses.csv.
• Refactored complex market clearing to incorporate zone information.
• Bids submitted with a specific node are now matched to the corresponding market zone.
• Fixed outputs.py store_grid function failing when buses.csv is missing x and y coordinates, since these are not required.

Testing

Implemented an extended example_1d with 4 nodes and 2 market zones and executed all three (redispatch, nodal, zonal) examples.

Checklist

Please check all applicable items:

• [x] Code changes are sufficiently documented (docstrings, inline comments, doc folder updates)
• [x] New unit tests added for new features or bug fixes
• [x] Existing tests pass with the changes
• [x] Reinforcement learning examples are operational (for DRL-related changes) - not applicable
• [x] Code tested with both local and Docker databases
• [x] Code follows project style guidelines and best practices
• [x] Changes are backwards compatible, or deprecation notices added
• [x] New dependencies added to pyproject.toml - not applicable
• [x] A note for the release notes doc/release_notes.rst of the upcoming release is included
• [x] Consent to release this PR's code under the GNU Affero General Public License v3.0

Additional Notes (if applicable)

[Any additional information, concerns, or areas you want reviewers to focus on]

Screenshots (if applicable)

[nick-harder]

Looks good. We could have a market_zones.rst or thelike which describes usage with buses.csv and so on and how this can be used for zonal and nodal clearing :)

@maurerle yes, I had that in mind, but me and Kim will be doing a case study in September using this funcitonality, and I believe some things might change, so the final documentation will follow there. I tried to describe as good as I can it in the docstrings. What I will prepare is a tutorial on using this functionality. And also a documentation on the configuration file with all the possible values and their explanation.