refactor(dashboard): dashboard improvements, codec & foveation presets

[Meister1593]

1. Improvements to sign about not running steamvr (easier to understand)
2. Added more notes to various places in dashboard and changed strings (statistics without connected client, debug tab for recording buttons, changed few notifications and added one more)
3. Added presets for foveation and codec
4. Adjusted all presets to go from low-to-high (or first disabled, then others)
5. Added a note to foveated encoding (to prevent users from disabling them without knowing the risks)
6. (internal) Higher order choice now uses display name for default value instead of indexes
7. Nvidia icd vulkan paths are now checked and chosen from two available ones and fallback to env param (i thought about finding first available, but using 32 bit vulkan icd most likely will break steamvr, playing it safe here)
8. Microphone on windows now disabled by default

[Meister1593]

Closes #2189

[zmerp]

beside the comments below, you have clippy and format to fix

[The-personified-devil]

I'm aware english is far from your first language, but running updated help strings through a grammar checker might be worthwhile as badly worded ones can make it even harder to understand what to do, especially if a user also isn't that good at english.

[zmerp]

This PR still needs fixing some lints, and replacing the critical tooltip with notice. I can work on notice first in another PR then you can rebase

[zmerp]

I was meaning to do a PR but I pushed to master by mistake... in any case this PR can be rebased, and use the new notice field string in place of the critical tooltip

[Meister1593]

I haven't noticed any issues with rounding that is caused by this PR, and actually for ex. latency overstep modifier being set to 0.999999 is fine, but UI rounds it to 1.0, only when i set it to 0.9999999 it rounds to 1.0 through rounding with this code

[The-personified-devil]

@zmerp You're right actually, however there's a simple workaround where it'll actually round to the number of valid places, not decimals (I got confused prior by assuming we were using this mode actually). See this example. This however does break larger integers at a certain point, so as I already mentioned we need to treat those separately. For floats however this should be perfect. However this should only be used in the comparison, not in the rounding when storing (which is kinda useless in the first place, but shouldn't really matter all things considered).

[zmerp]

Good call, we should use the .Xe notation then, and exclude integers

[zmerp]

@The-personified-devil @Meister1593 Let me know if this is mergeable. I am aware of the disagreement on how to handle float comparison. The current method is affected by these issues: https://play.rust-lang.org/?version=stable&mode=debug&edition=2024&gist=5657af39041c776b9957976adaa93a53
But for what we want, we shouldn't need a workaround for this, potentially with a non-negligible cost, any time soon.

[Meister1593]

I'm okay with any solution that works with that really, comment should suffice for the time being

[The-personified-devil]

Only that one thing btw, after that the pr is fully done and ready to merge.

[zmerp]

The value equality check should be fixed for real now