docs: port to VitePress

Things that happen in this shameless squash:
- Removed 404 page
  - It doesn't work in VitePress and making it work in VitePress needs
    some invasive hack in the theme that I'm not willing to do
  - The default is more than enough, though
- Moved consoleVersionSelect include to another directory
  - This avoids being uploaded to Crowdin for translation
- Inline all SafeB9SInstaller includes
  - Not only do parameterized includes not work, but if/else statements
    don't work at all
- The sysupdate include parameter hasn't been used since MSET9, so it
  actually works just fine without any parameters. Hooray(?)
- Move mset9-chorus to an include, that logic doesn't work in VitePress
- Removed Get Started button from homepage, it breaks translations
- Tables in get-started are now shown by default; it seems VitePress really does
  not want us to use inline script. So we cannot enable it upon
  realizing that the browser is JS capable
- Include parameters are now in frontmatter to allow translation
- Hacked in a bunch of CSS values kanged from the old theme to make it
  look not stupid
- Drop headers down one level to make table of contents work

docs/checking-for-cfw.md

@@ -1,43 +1,58 @@
----
-title: "Checking for CFW"
----
+# Checking for CFW
 
-{% include toc title="Table of Contents" %}
-
-### Required Reading
+## Required Reading
 
 This is an add-on section to check if your console already has a modern custom firmware.
 
 If your console already has an arm9loaderhax or boot9strap based custom firmware, you will need to follow the instructions indicated to upgrade your setup to a modern one.
 
-If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#other-troubleshooting), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
-{: .notice--info}
+::: info
 
-### Instructions
+If your console has a menuhax-based CFW setup, you should [clear HOME Menu's extdata](troubleshooting#other-troubleshooting), then follow all instructions on your SysNAND. You probably have a menuhax-based setup if your system version when booting without an SD card is 9.2.0-20.
+
+:::
+
+## Instructions
 
 1. Power off your console
 1. Hold the (Select) button
 1. Power on your console while still holding the (Select) button
 1. You should now see a configuration menu of some sort
 
-___
+## What to do next
 
-### What to do next
+::: tip
 
 If your console boots to the normal HOME Menu, return to [Get Started](get-started)
-{: .notice--success}
+
+:::
+
+::: tip
 
 If you see a Luma3DS version of 7.0.5 or lower, continue to [A9LH to B9S](a9lh-to-b9s)
-{: .notice--primary}
+
+:::
+
+::: tip
 
 If you see a Luma3DS version of 7.1, continue to [Updating B9S](updating-b9s)
-{: .notice--primary}
+
+:::
+
+::: tip
 
 If you see a Luma3DS version of 8.0 or greater, continue to [Restoring / Updating CFW](restoring-updating-cfw)
-{: .notice--primary}
+
+:::
+
+::: warning
 
 If you see GodMode9, Decrypt9WIP, Hourglass9, or Luma3DS chainloader, you held (Start) by accident and should try these instructions again with (Select)
-{: .notice--warning}
+
+:::
+
+::: danger
 
 If you see something not described by the above options, join [Nintendo Homebrew on Discord](https://discord.gg/MWxPgEp) and ask, in English, for help.
-{: .notice--danger}
+
+:::