feat(build): use jekyll and restyle website

[ReenigneArcher]

Description

This PR moves the website to a Jekyll build.

Todo:

• update build workflow
  • This build works, but could be simplified... investigate... https://github.com/ReenigneArcher/beautiful-jekyll/blob/b8e13290831a3160751761ecce52800c694560f3/.github/workflows/ci.yml#L59-L72 ... e.g. there would be no gh-pages branch
• fix some colors (see support.html)
• determine a plan to build subproject sites (like Sunshine)
  • probably have to maintain a modified fork of beautiful-jekyll to use as a theme
  • alternatively a github action that can be used
• update first blog post date
• remove dist directory
• add privacy/terms
  • links in footer
• convert readme to markdown
• run workflow when new posts are added to master branch?
• release notifier to create a new blog post automatically
• remove discord widget from discord.html page
• don't search all pages (if possible)... only search blog posts
• hide titles on some pages, and add title to pages that don't have it (e.g. discord.html)
• update gh-pages from other repos that use assets from the published site (move them to jekyll build)
  • Sunshine
  • ThemerrDB ... (archived)
  • GamesDB
• update any projects that use assets from the published site
  • Sunshine
  • Themerr-plex (discord widgetcrate) ... (archived)
  • ThemerrDB (gh-pages) ... (archived)
  • GamesDB (gh-pages)
  • Themerr-jellyfin? widgetbot?
  • .github (readthedocs)
• probably wait for bs5 before merging this: build(deps): bump bootstrap from 4.4.1 to 5.5.3 daattali/beautiful-jekyll#1375

Screenshot

Original jekyll theme

Updated jekyll theme (to match existing site)

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components