[BUG]: WebGL debugging: unclear origin of regl.clear() warnings in scattergl rendering

Description

While working on issue #7387 and the associated fix (#7390), I noticed that debugging WebGL-related warnings (specifically those related to regl.clear()) can be difficult due to a lack of contextual information about where the call originates.

In strict or debug environments, warnings such as:
"clear() called with no buffers in bitmask"
may appear without clearly indicating which rendering path or trace triggered them.

This makes it harder for contributors and developers to trace the source of the issue, especially when working with scattergl or other WebGL-based traces.

Steps to Reproduce

1. Use a WebGL-based trace (e.g., scattergl)
2. Run in a development or strict/debug environment
3. Trigger a render/update cycle
4. Observe WebGL warnings in console

Expected Behavior

Warnings should provide enough context to help identify:

• which trace type triggered the call
• where in the rendering pipeline it originated

Actual Behavior

Warnings appear without clear contextual linkage to the rendering path, making debugging less efficient.

Suggested Improvement

Consider improving developer experience by:

• adding contextual debug information (e.g., trace type or module)
• documenting expected regl.clear() usage more explicitly
• optionally enhancing debug logging in development mode

Additional Context

This observation is based on my contribution to fix issue #7387:
https://github.com/plotly/plotly.js/issues/7387

Inizia esaminando l’issue #7387 e il fix associato #7390, quindi traccia il percorso di rendering di scattergl che può chiamare regl.clear(). L’issue non indica file né test; il lavoro sarà completato quando esisterà un’implementazione concordata che permetta agli avvisi di identificare il trace o la posizione di rendering che li attiva e verifichi l’output di debug risultante.