v2: Rewrite

[drweissbrot]

• Players Alive panel
• Focused Player panel
• Top Bar
• "Series Name" panel
• Radar
• Sidebars
• Series and Round Graph panel
• Make sure everything that reasonably should is a CSS variable, and components, methods, etc. are reasonably split up
• Cleanup

I've learned a couple things since I originally started building this. Some design decisions were, in hindsight, not great; usually because the original target audience of this was only myself. But since there is at least one other person using this who currently has to live with my shoddy code, and with CS2 coming at us any decade now, I think now's as good a time as any to restart this project from scratch, and replace the old bad design decisions with new, hopefully-less-bad design decisions.

Primary goals:

• CS2 support
  For now, this means preparing everything to eventually work with CS2, i.e. decoupling the "data layer" from the raw GSI payloads. There's currently no demo viewer, no GOTV, and no GSI in the Limited Test. I'm assuming all of these will return; if they don't, I think it may be possible to write a LUA addon or something to mimic GSI.
• Easier customization
  Judging from the forks of this repo, most users of this HUD are fine with the general look, but want to apply their own color scheme. This should be easy to do, without having to fork the repo (and in turn, making updates more difficult). Heavier customization should be possible too, also without having to fork. In general, forks should be for bug fixes and feature additions, not for customization.
• Easier extensibility
  There are a couple features I and other users would like that are currently very hard/annoying to implement because the code was not written with extensibility or maintainability in mind.
• OBS Browser Source
  Likely a better approach than the current "Fullscreen Windowed plus Display Capture" flow.

Additionally, I'd like to eventually have prepackaged exectuables with update checking (#60), container images (#61), docs + changelog (#59), and a landing page to showcase the project (#62).

For this Issue, the goal is a functioning MVP, that looks similar to the current version, supports the primary customization features, and is accessible as a web page.