Add retry mechanism for default online style fetches that fail due to network errors

We have some application code that attempts to update the displayed map from the offline fallback to the online style when the network is connected again. However, network being "connected" does not necessarily mean that internet access is available and getting that information can be limited based on which APIs you have access to. For example, desktop uses the window online event, which only reflects when you regain access to a network but makes no guarantees about access to the internet.

To my knowledge, fetch calls that fail due to lack of internet connection do so immediately i.e. no configurable timeout to wait for. Given this, I think it would make sense to set up a retry for the online style if that kind of failure does occur.

Locate the application code that updates the displayed map from the offline fallback to the online style, then inspect how the desktop window online event triggers the fetch. Add retry behavior for online-style fetches that fail from unavailable internet access, and verify that a failed fetch is retried when connectivity is actually restored.