Optimize UI CPU usage

[Gold856]

Description

This fixes the JSON.stringify hack used to check if the current camera settings was PlaceholderCameraSettings by using Object.freeze (this apparently allows normal equality operators to be used). This takes CPU usage down a few extra percent. One dynamically calculated class was also removed because those are also CPU-expensive (and this instance was completely unnecessary and easy to remove. Doesn't have much impact though.)

Fixes #2159.

Meta

Merge checklist:

• Pull Request title is short, imperative summary of proposed changes
• The description documents the what and why
• If this PR changes behavior or adds a feature, user documentation is updated
• If this PR touches photon-serde, all messages have been regenerated and hashes have not changed unexpectedly
• If this PR touches configuration, this is backwards compatible with settings back to v2025.3.2
• If this PR touches pipeline settings or anything related to data exchange, the frontend typing is updated
• If this PR addresses a bug, a regression test for it is added

[samfreund]

Is the goal here to optimize CPU usage on the client or the coprocessor?

[Gold856]

On the client.

[Gold856]

Apparently whether or not my laptop is plugged in makes a huge difference in CPU usage percentage (I assume this is a relative thing and my CPU is downclocking when unplugged). When unplugged, old baseline for main is ~70%, this PR (when it removed the loading SVG from the DOM and stuffed it into an ) brought it down to ~30%, 2025.3.1 baseline is ~12%. The difference is caused by the animated Camera Matching tab when no cameras are configured.

[DevonRD]

lgtm!