Add additional WebGL filter stress scenarios to visual regression suite

Increasing access

Adds more WebGL filter scenarios to the visual regression suite so rendering issues can be caught earlier. This makes it easier to verify changes and reduces the chance of unnoticed breakage across releases.

Most appropriate sub-area of p5.js?

• Accessibility
• Color
• Core/Environment/Rendering
• Data
• DOM
• Events
• Image
• IO
• Math
• Typography
• Utilities
• WebGL
• Build process
• Unit testing
• Internationalization
• Friendly errors
• Other (specify if possible)

Feature enhancement details

While working on #8549 , I manually tested a few additional WebGL filter interaction scenarios that are not currently covered by the visual regression suite.

The current suite covers individual filters and some chained combinations, but does not cover:

• Filters applied after texture() on WebGL geometry
• Filters on createGraphics(WEBGL) buffers
• Filters after resizeCanvas()
• Filters with pixelDensity(2)
• Additional chained combinations beyond existing coverage

These scenarios behaved consistently across versions during manual testing. It may be useful to formalize them into automated visual tests to improve regression detection in future releases.

Start by locating the visual regression suite and its existing WebGL filter scenarios. Review how current filter snapshots are defined, then add coverage for filters after texture(), createGraphics(WEBGL), resizeCanvas(), pixelDensity(2), and additional chained combinations. Run the visual regression tests and confirm the new scenarios produce stable expected results.