Upgrade/improved antimeridian logic

[abradley60]

• Adding doc string for cop30 function
• Converting bounds and BoundingBox logic to (left, bottom, right, top)
• Removing shape/polygon related logic for antimeridians
• The assumption is a correct set of bounds for the antimeridian has left > right
• If a set of bounds seems like it may cross the antimeridian, a warning is raised (see README.md)
• Branch has been tested with antimeridian scene insar-pipeline
• Adding a specific test for an antimeridian DEM
• Fixing a bug where the shape of an antimeridian dem returned is different than a regular dem. I.e. when antimeridian a (1,X,Y) dem is returned when a (X,Y) dem shape should be returned from the function.

[abradley60]

TODO - Add a specific test for comparing a DEM over the antimeridian

[abradley60]

TODO - Add a specific test for comparing a DEM over the antimeridian

Done ✅

[caitlinadams]

Looks great! I've made a few minor suggestions, and added a comment indicating where we may need to check that a modified set of bounds still falls within the valid extent ranges: y = (-90, 90), x = (-180, 180)

[caitlinadams]

This looks good to me. I think there's still a few of my suggestions that haven't been accepted. I've also suggested we remove the unicode ticks, since I don't think we use them elsewhere.