Incorrect landmark data (?) in city center of Amsterdam

Nobody has claimed this yet.

### mapbox-gl-js version

v3.17

### Browser and version

Firefox 146.0.1

### Expected behavior

No error in the console.

### Actual behavior

Panning and zooming through the city center of Amsterdam, will eventually cause an error in the console:

**Object { message: "can't access property Symbol.iterator, t.json.meshes is undefined", stack: "" }**
​
message: "can't access property Symbol.iterator, t.json.meshes is undefined"
​
stack: ""
​
: Error.prototype { stack: "", … }
[evented.ts:174:21](https://api.mapbox.com/mapbox-gl-js/src/util/evented.ts)
fire evented.ts:174
fire evented.ts:168
fire evented.ts:168
_tileLoaded source_cache.ts:266
r tiled_3d_model_source.ts:186
processTask actor.ts:162
receive actor.ts:144
(Async: EventListener.handleEvent)
Gd actor.ts:54
Zd dispatcher.ts:40
Po style.ts:420
_updateStyle map.ts:2366
setStyle map.ts:2337
Map map.ts:744
check-for-support-demo.html:1

### Link to the demonstration

https://docs.mapbox.com/mapbox-gl-js/example/check-for-support/

### Steps to trigger the unexpected behavior

Zoom in and pan on the city center of Amsterdam in the Netherlands

### Relevant log output

```shell
Object { message: "can't access property Symbol.iterator, t.json.meshes is undefined", stack: "" }
​
message: "can't access property Symbol.iterator, t.json.meshes is undefined"
​
stack: ""
​
: Error.prototype { stack: "", … }
evented.ts:174:21
fire evented.ts:174
fire evented.ts:168
fire evented.ts:168
_tileLoaded source_cache.ts:266
r tiled_3d_model_source.ts:186
processTask actor.ts:162
receive actor.ts:144
(Async: EventListener.handleEvent)
Gd actor.ts:54
Zd dispatcher.ts:40
Po style.ts:420
_updateStyle map.ts:2366
setStyle map.ts:2337
Map map.ts:744
check-for-support-demo.html:1
```

Reproduce the issue in the check-for-support demo by zooming and panning over Amsterdam, then trace the reported call path through tiled_3d_model_source.ts, source_cache.ts, and evented.ts. Done means the Amsterdam view no longer produces the reported console error.

Written by the indexing model from the issue text.