[Feature Request]: Move Cluster's `geo_json` to `GeographicalInformation`

### Preflight Checklist

- [x] I have read the [Contributing Guidelines](https://github.com/EnAccess/micropowermanager/blob/main/CONTRIBUTING.md) for this project, if it exists.
- [x] I agree to follow the [Code of Conduct](https://github.com/EnAccess/micropowermanager/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://github.com/EnAccess/micropowermanager/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

It's bit inconsistent, that Cluster simple has their geo information stored at the main object.

### Proposed Solution

Just use `GeographicalInformation`. Note, this only works after `GeographicalInformation` has been refactored to affect `geo_json` instead of hard coded points.

### Alternatives Considered

N/A

### Additional Information

_No response_

Start by inspecting the Cluster and GeographicalInformation classes and how their geographical data is currently represented. First understand the required refactor so GeographicalInformation affects geo_json rather than hard-coded points; the work is done when Cluster uses GeographicalInformation for geo_json consistently and the existing geographical behavior remains correct.

Written by the indexing model from the issue text.