Upgrade Three.js for better performance

[takahirox]

Is your feature request related to a problem? Please describe.

getProgramCacheKey() in Three.js seems to be one of the performance bottlenecks.

Describe the solution you'd like

The performance of it seems to be improved in r136. Maybe worth to upgrade our Three.js to the latest

mrdoob/three.js#22960

Additional context

Three.js we use now is r133 based

[blairmacintyre]

Just talked with Rik about issues I'm having on Quest2, and he pointed to some fixes in 137 that will help perf (multisampling and layers) and solve my issues (custom shader related).

I too am wondering if upgrading is feasible.

[takahirox]

Status: I'm working on upgrading Three.js but encountered some weird problem on compilation with npm run dev.

[takahirox]

@blairmacintyre Still a bit at testing phase but I made a PR #5488 . You can locally merge and test.

[blairmacintyre]

@takahirox I'm not sure I can test this; it's against the main branch of the hubs client, but we're using the hubs-cloud branch.