GeoboxTiles.tiles gives wrong results for global inputs

[Kirill888]

GeoboxTiles.tiles takes in a geometry in any projection and returns an iterator over tiles that overlap with the given geometry. In order to do that, it first needs to project input shape into a CRS native to GeoboxTiles. This breaks down when source shape covers area way outside of the valid region of the destination CRS, as a result instead of returning all the tiles nothing is returned at all. Essentially this step Geometry@crs1 -> BoundingBox(Geometry@crs2) produces wrong results, this is especially common when source image has "global coverage" and destination CRS has a limited range like epsg:3577 for example.

What's needed is a robust "bounding box of a geometry in some other projection method", that does not slow down the common case where source shape is in a safe region for coordinate transformation. Ideally we would also have a "robust to_crs method for polygons" that would safely clip sections of the source geometry that are outside of the valid range of transform.