Approaching goofy levels of testing

There's a few unconventional things that I'd like to add some equally unconventional tests for. Namely:

- [x] Test that the linker strips away unused embedded assets
- Have different integration tests that make use of embedded assets. Do an optimized build then inspect the `.rodata` section of the binary to verify whether or not they're included
- [x] Add a watchdog test to keep track of our `syntect` version and manually enter in relevant info for the assets sizes and an identifying fingerprint for testing if they're in the `.rodata`
- [ ] Add a release workflow that ensures the assets are up-to-date. The asset generation seems stable now that the `Cargo.lock` file is committed (on linux at least, but that's what we run in CI, so no problem there)
- Specifically this would be a release workflow instead of a regular CI run because I don't want to have a ton of churn that winds up bloating our git history (on second thought maybe we make it into a regular test and we just `#[ignore]` it while it's broken and have the release workflow run ignored tests?
- [ ] Add a watchdog test that generates the syntax table. It easily goes out of sync
- Covers #39
- [ ] Add a watchdog test that diffs the docs landing page and the readme to help ensure they stay in sync (the landing page could be automatically generated and stored in a test)