[Bug] Warnings with HexagonLayer starting with version 9.1.0

Description

Starting with version 9.1.0 (no problem with 9.0.41), the following warnings are shown in the console when using HexagonLayer:

WebGL: INVALID_OPERATION: vertexAttribPointer: no ARRAY_BUFFER is bound and offset is non-zero (shown twice)
WebGL: INVALID_OPERATION: drawArraysInstanced: no buffer is bound to enabled attribute

(In my application, after updating deck.gl to 9.1.x, I also started getting

deck: Features not supported by GPU aggregation, falling back to CPU
WebGL: INVALID_VALUE: texSubImage2D: width or height out of range
[.WebGL-0x5c840006a200] GL_INVALID_VALUE: Desired resource size is greater than max texture size.

and the hexagons are not shown, but perhaps the cause for my warnings is also the cause for the warnings about INVALID_OPERATION.)

Flavors

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

Expected Behavior

No warnings, as it was the case with the versions 9.0.x

Steps to Reproduce

Check the console for this example and this example from the docs.

Environment

• Framework version: 9.1.x
• Browser: Firefox, Edge, Opera, Chrome
• OS: Windows, Android

Logs

WebGL: INVALID_OPERATION: vertexAttribPointer: no ARRAY_BUFFER is bound and offset is non-zero
WebGL: INVALID_OPERATION: vertexAttribPointer: no ARRAY_BUFFER is bound and offset is non-zero
WebGL: INVALID_OPERATION: drawArraysInstanced: no buffer is bound to enabled attribute

Start with the HexagonLayer API example and hexagon-layer example linked in the issue, reproducing the console warnings on deck.gl 9.1.x and comparing them with 9.0.41. Trace the HexagonLayer rendering and GPU aggregation path from those entry points; done means the examples render hexagons without the reported WebGL warnings or fallback errors.