Generate and publish shotover website

[rukai]

This PR demonstrates the full website via github pages implementation.
It is temporarily hosted here: https://shotovertest.rukai.xyz/ (running from my github fork of the repo)
And can be compared to the current website at https://shotover.io/

Once the website is deployed we need to follow the steps at https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site for github.com/shotover/shotover-proxy with shotover.io domain.

The current website implementation is hosted at https://github.com/shotover/shotover-website , it is implemented with an early alpha release of vuepress. I previously attempted to upgrade to a modern version of vuepress but gave up because the upgrade changed all kinds of css/html leaving the formatting broken.

This PR implements the website via a new website crate in the cargo workspace.
Running the website crate generates the website at website/root, by following these steps:

• Generate the landing page index.html
  • The landing page is generated from a manually stripped down version of the original website, this avoids the npm dependency and makes the site faster to load.
• Generate the documentation index docs/index.html
  • Links are generated for all the documentation generated in the following steps (except main branch docs which are intentionally hidden)
  • Shares css and base html template with the landing page.
• Generate main docs docs/main
  • Run mdbook on the current state of the repo
    • mdbook was what we originally used for documentation before the shotover website rewrite. The rewrite never quite had proper compatibility with the original mdbook, so swapping back to mdbook will improve compatibility.
• Generate docs for every released version docs/x.y.z
  • Clone another shotover repo from the latest github.com/shotover/shotover-proxy, run git tag to find the latest version of breaking releases and then generate mdbook docs from the sub repo after checking out each tag.
• Generate docs for the latest released version docs/latest
  • Take the latest release from the step and regenerate it at docs/latest

Intentional changes to the landing page of the original website:

• The navbar at the top has underlined links, makes it easier to tell they are navigation.
• The image of the shotover river at the very bottom is left out, I'm pretty sure we dont actually have the rights to use this image.
• I removed the light/dark mode button, instead light/dark mode is determined from the users system preferences for ligh/dark mode.
  • I see no value in providing the option, just use what the user prefers by default.

• I removed the stock images from "What problems does Shotover solve?" section, they are probably from the original template and dont really have any meaning here.

Reviewing

I will split the PR up into 2 separate PRs for easier review:

• publish docs to /docs/main #1854
• This PR

[codspeed-hq]

CodSpeed Performance Report

Merging #1853 will not alter performance

_{Comparing rukai:publish-pages (e7d71e7) with main (21a0ff7)}

Summary

✅ 38 untouched benchmarks

[justinweng-instaclustr]

Overall LGTM.
Just a minor comment. The original doc page has this Shotover logo at the top right corner that allows you to go back to the home page while the new doc page doesn't provide the way to navigate back anymore. Is this intended?

[rukai]

It is currently intended, mdbook does provide a way to add some custom html, and I would like to use that functionality to reintroduce a link back to the landing page at sometime, but its not a priority right now.