Add support for lat-lon coordinate pairs for the property boundaries and no-go zones

[mitchute]

Issue overview

The title is self-explanatory. I think we can do a simple cartesian conversion to accomplish this and not add another dependency, such as geopy.

[chriswmackey]

I just noticed that this was opened here just before I added very similar functionality into the ThermalNetwork package, which uses a GeoJSON following the URBANopt schema to size ground heat exchangers with GHEDesigner.

I didn't realize that there were also plans to add support for this natively within GHEDesigner. I can confirm that this is definitely true:

I think we can do a simple cartesian conversion to accomplish this and not add another dependency

Pretty much all Lat/Long conversion these days is done using a simple ellipsoid model of the Earth that's referred to as the WSG-84 model. The math to convert between Lat/Long and Meters is very simple and you can find it here in this module that I contributed to ThermalNetwork:
https://github.com/NREL/ThermalNetwork/blob/main/thermalnetwork/projection.py

Feel free to take that same code and make use of it here if desired.