Improve raster overlay error reporting and handling

[kring]

Previously, if a raster overlay tile provider ran into an error while loading overlay images (for example, if a WMS server returned an error because it didn't support EPSG:4236), those errors were ignored, and the tileset wouldn't show up at all. This was pretty unhelpful for users, who had no way to learn what was happening except by using the debugger. With this PR:

1. Errors loading raster overlays are logged.
2. Raster overlay failures will no longer stop the geometry tile they're attached to from rendering. Instead, once the image load fails, the geometry tile will simply be rendered without any raster overlay.

[j9liu]

@kring This looks good to me! I wanted to verify the behavior where tilesets can still load with erroneous overlays, but if I don't get to it in time it's okay to merge.

[j9liu]

@kring I tested this in Unreal with a Cesium ion raster overlay draped on CWT, and set it to a non-imagery asset ID (like 1). Unfortunately this did prevent CWT from rendering. But maybe this case is special?

In any case I also tested this with an invalid WMS base URL, and found that it still prevented CWT from rendering... I swear I'm using this branch and that I rebuilt the extern folder. :')

Do you see something different? Maybe I'm testing the wrong cases?

[kring]

That should be working now @j9liu. I was testing with raster overlays that could successfully create a tile provider, but then all of the tile loads failed. In your (perfectly valid) test, the tile provider creation itself was failing. That's handled now, too.

[j9liu]

Thanks @kring! I tested with the same cases I wrote above and the tileset's no longer blocked by the invalid overlay. I also see errors related to raster overlay tiles being logged to the console. Merging now!