Mapbox Studio Filter Expression triggering high memory usage and slower framerate.

Nobody has claimed this yet.

The below filter expression is triggering a warning saying:

```
Failed to extract static filter. Filter will continue working, but at higher memory usage and slower framerate.
This is most likely a bug, please report this via https://github.com/mapbox/mapbox-gl-js/issues/new?assignees=&labels=&template=Bug_report.md
and paste the contents of this message in the report.
```

I'm doing my part! 🫡

```
Filter Expression:
[
"all",
[
">",
[
"get",
"way_area"
],
150000
],
[
"any",
[
"!",
[
"in",
"park",
[
"downcase",
[
"case",
[
"==",
[
"get",
"name"
],
null
],
"",
[
"get",
"name"
]
]
]
]
],
[
"!",
[
"in",
"park",
[
"downcase",
[
"case",
[
"==",
[
"get",
"name"
],
null
],
"",
[
"get",
"name"
]
]
]
]
]
],
[
"case",
[
"<=",
[
"pitch"
],
45
],
true,
[
"<=",
[
"distance-from-center"
],
2
]
]
]Filter Expression:
[
"all",
[
">",
[
"get",
"way_area"
],
150000
],
[
"any",
[
"!",
[
"in",
"park",
[
"downcase",
[
"case",
[
"==",
[
"get",
"name"
],
null
],
"",
[
"get",
"name"
]
]
]
]
],
[
"!",
[
"in",
"park",
[
"downcase",
[
"case",
[
"==",
[
"get",
"name"
],
null
],
"",
[
"get",
"name"
]
]
]
]
]
],
[
"case",
[
"<=",
[
"pitch"
],
45
],
true,
[
"<=",
[
"distance-from-center"
],
2
]
]
]
```

The issue names no repository file, test, or entry point. Start by reproducing the supplied filter expression and tracing the source of the “Failed to extract static filter” warning. Done means identifying the expression path responsible for the warning and verifying the resulting memory and framerate behavior after a fix.

Written by the indexing model from the issue text.