Addons: Remove GPUStatsPanel.

[Mugen87]

Related issue: #29295

Description

This PR removes the addon GPUStatsPanel. For more detailed performance monitoring, it's best to use https://github.com/RenaudRohlinger/stats-gl since it works for both WebGL and WebGPU.

As mentioned earlier, ideally stats-gl replaces the original stats.js in the examples at some point. Since there seems to be some issues in context of Safari and M processors (see #28978), it's probably best to wait a bit until these problems have been resolved.

[gkjohnson]

Does it make sense to remove this before stats-gl properly replaces stats.js? I still use this plugin and have used it to benchmark changes to some of the examples that it's removed from in this PR.

[Mugen87]

Can you switch instead to stats-gl on your side? If you put the following into an example's import map, you can import via import Stats from 'stats-gl'; and use it as a replacement of stats.js.

"stats-gl": "https://cdn.jsdelivr.net/npm/[email protected]/dist/main.js"

I have the feeling this is better than retaining GPUStatsPanel which is simply rendundant.

[gkjohnson]

I'm just suggesting to not remove stats.js related components until stats.js is removed from the project. But I see that stats-gl is basically the same thing.

[mrdoob]

How about replacing GPUStatsPanel with stats-gl in those examples instead?

[Mugen87]

Done!

[RenaudRohlinger]

Regarding stats-gl, I’m considering disabling the GPU metrics by default.
Since this is the only metric currently causing issues and is quite advanced, its default state might be better set to off, especially given that it’s not entirely accurate. The CPU metric, on the other hand, is both stable and highly useful, which could be sufficient to drive adoption and facilitate the transition from stats to stats-gl. /cc @Mugen87

[RenaudRohlinger]

Released [email protected] which doesn't have the GPU metrics by default.