[Bug] HeatmapLayer breaks when used with DataFilterExtension and other extensions

Description

Hi - I noticed that the DataFilterExtension specifically calls out support with the Heatmap layer, however I am experiencing strange behaviour.

It seems as soon as a data range is applied, the heatmap fails to render.

Flavors

• Script tag
• React
• Python/Jupyter notebook
• MapboxOverlay
• GoogleMapsOverlay
• CartoLayer
• ArcGIS

Expected Behavior

The heatmap render points that satisfy the filter

Steps to Reproduce

Please see a codepen example here
This uses the SF bikes data, and filters the data by spaces available.
Notice that if the range is changed to [0,10] the entire heatmap renders again. This is strange as there are lots of points in the range [1,10]

Environment

• Framework version: 9.0.14
• Browser: Chrome 124.0.6367.80
• OS: MacOS

Logs

"luma.gl: Module picking not found"
"luma.gl: Unknown binding 'project32Uniforms' in render pipeline 'HeatmapLayer-triangle-layer-cached', expected one of 'maxTexture', 'weightsTexture', 'colorTexture'"
"luma.gl: Model(HeatmapLayer-triangle-layer): Missing layout for buffer 'filterValues'."
"luma.gl: Model(HeatmapLayer-triangle-layer): Missing layout for buffer 'instanceFilterValues'."
"luma.gl: Model 'HeatmapLayer-triangle-layer: Ignoring constant supplied for unknown attribute 'instancePickingColors'"
"luma.gl: Module picking not found"
"luma.gl: Unknown binding 'project32Uniforms' in render pipeline 'HeatmapLayer-triangle-layer-cached', expected one of 'maxTexture', 'weightsTexture', 'colorTexture'"

Reproduce the failure in the linked CodePen with HeatmapLayer and DataFilterExtension, especially when the range is [0,10]. Start by tracing the HeatmapLayer and DataFilterExtension entry points against the reported luma.gl pipeline and buffer errors; done means filtered points render without those errors.