refactor: migrate GeoInfo points filed into GeoJSON data scheme via geo_json field

[beesaferoot]

Ths PR carries out a large but crucial refactor before landing MPM v1.0. This continues a string of refactors that replaces changes existing location data into on consistent standard GeoJSON format.

Closes #1035

Brief summary of the change made

Are there any other side effects of this change that we should be aware of?

Describe how you tested your changes?

Pull Request checklist

Please confirm you have completed any of the necessary steps below.

• Meaningful Pull Request title and description
• Changes tested as described above
• Added appropriate documentation for the change.
• Created GitHub issues for any relevant followup/future enhancements if appropriate.

[dmohns]

Really nice!! Looking forward to it. Few comments

[dmohns]

Nice!!! Last question... can you expand why you chose jmikola/geojson? It seems a bit inactive, last commit 3 years ago, only tested against PHP 8.2. Compared to the more active brick/geo ?

[beesaferoot]

Nice!!! Last question... can you expand why you chose jmikola/geojson? It seems a bit inactive, last commit 3 years ago, only tested against PHP 8.2. Compared to the more active brick/geo ?

brick/geo comes with a ton of features we don't utilize more than constructing a GeoJSON object i.e performing operations on these objects. While jmikola/geojson implements the GeoJSON format specification and doesn't add anything else; which I think is just right for our use case.

I didn't think we needed a dependency that we don't use 99% of its features.