Add analytics for wgpu backend and whether the viewer runs in WSL

[Wumpf]

Today we're driving blind on some of the key questions around Rerun Viewer usage. This PR adds three new properties to the viewer_started analytics event:

• is_wsl
  • a boolean indicating whether the viewer has been started directly from the WSL
  • we're interested in this because we want to understand the importance of WSL support
• graphics_adapter_backend
  • a string identifying which of the wgpu backends is used
  • we're interested in this because we want to know which graphics backends are the most important
    • The most important distinction here is gl (webgl + desktop gl) vs webgpu vs everything else. We want to understand when the right time is to phase out support for gl.
• re_renderer_device_tier
  • a string identifying which of the (today two) device tiers re_renderer settled on for a given viewer session
  • similar to the above this gives us a (very) rough idea of what abilities the graphics adapter has
  • it's likely that we'll add one or two more tiers in the future

---

As always we're trying to be considerate with what we add to our analytics in order to be intrusive while providing valuable information to inform the development of Rerun.
If you want to learn more about analytics run rerun analytics details.
If you have a complaint about the intrusiveness of these analytics please reach out.

---

Examples of what we see on Posthog with this:

Starting viewer on Windows:

Starting viewer from WSL (with #8610 merged in):

Starting the viewer from the Browser @ WebGL:

Starting the viewer from the Browser @ WebGPU:

[github-actions]

Web viewer built successfully. If applicable, you should also test it:

• I have tested the web viewer

Result	Commit	Link	Manifest
✅	37e8123	https://rerun.io/viewer/pr/8612	+nightly +main

^{Note: This comment is updated whenever you push a commit.}

[emilk]

nice