Allow Safari to use the Image API to decode images to avoid a potential crash

[ryanhamley]

Launch Checklist

• briefly describe the changes in this PR
  • This reverts part of the change in Always retain raster tile cache control data #10494 and only uses window.createImageBitmap to decode images when offscreenCanvas is supported. OffscreenCanvas is not supported by Safari which forces Safari to decode images using the Image API. Certain types of WebP images (raster-dem tiles over the ocean with small or no variation in them) cause Safari 15.2 and Safari 15.3 to crash when decoded with createImageBitmap. With the Image API, these images still fail to decode, but Safari properly handles the error so the failure is harmless.
  • The upside of this change is that we can continue requesting WebP images which are significantly smaller than PNG images but we avoid the Safari tab crashing.
  • The original bug for the Safari crash is 3d terrain crashes Safari 15.3 #11494
  • The offscreenCanvasSupported() check was first added in ImageBitmap and OffscreenCanvas for DEM tiles #8845 as a progressive enhancement.
• manually test the debug page
  • Without this change, Safari 15.2/15.3 consistently crashes with certain tiles. With this change, Safari gracefully handles the bug by logging an error.
• apply changelog label ('bug', 'feature', 'docs', etc) or use the label 'skip changelog'
• add an entry inside this element for inclusion in the mapbox-gl-js changelog: <changelog>Allow Safari to use the Image API to decode images to avoid a potential crash</changelog>

This is a public style and location I used to manually test this.

var map = window.map = new mapboxgl.Map({
    container: 'map',
    zoom: 14.14,
    center: [-118.39997, 33.75873],
    style: 'mapbox://styles/ryanhamley/ckzhfiobs001i16kdrvuo8isv',
    hash: true
});

[ryanhamley]

@mourner I changed this to check for Safari so that Firefox can still use createImageBitmap and get the benefits of that. Can you re-review?

[karimnaaji]

Is it possible for this type of check to be more granular and check for version number in the user agent?
e.g. isSafari(window, '15.3')). If this is fixed in 15.4, maybe it wouldn't make sense to prevent this code path for all future Safari versions, so users can still benefit from #10491.

[ryanhamley]

Closing since this issue was fixed on the server-side