Switching away from the map while it is loading causes a `t.getActor() is undefined` error that cannot be caught before it has been logged to the console

Nobody has claimed this yet.

**mapbox-gl-js version**: 1.6.1

**browser**: Firefox 120.0 (64-bit)

### Steps to Trigger Behavior

1. Have two pages, one where the map is loaded
2. Switch to the other page when the map object has been created but before it starts rendering any tiles
3. You will then see various "Uncaught TypeError: t.getActor() is undefined" console errors

### Expected Behavior

Have a way to stop this from happening.

### Actual Behavior

I cannot stop this error from being output to the terminal.
- I've tried wrapping the `new mapboxgl.Map` call in a try catch but that does not get triggered likely because the problematic `cacheEntryPossiblyAdded mapbox-gl.js:29` call is actually a callback.
- Same with defining a `map.on('error'` right after the map creation, the error doesn't seem to go through that flow for some reason.

Reproduce the issue by switching pages after the map object is created but before tiles render, then inspect the cacheEntryPossiblyAdded callback around mapbox-gl.js line 29. Check how this asynchronous error relates to new mapboxgl.Map and map.on('error'); done means the page switch no longer logs an uncaught t.getActor() error.

Written by the indexing model from the issue text.