Upgrade to Docusaurus v3

[tukib]

Note

Upgrading multiple packages rather than in sequence is an exception to our current policy. The justification for this is that Docusaurus v3 directly requires our MDX and React versions to match. Attempting to upgrade these separately may cause issues and additional overhead.

All dependencies below are already at their latest minor & patch version. Resolves #34

Dependency	Current	New
@docusaurus/core	^2.4.3	^3.0.0
@docusaurus/plugin-content-docs	^2.4.3	^3.0.0
@docusaurus/theme-classic	^2.4.3	^3.0.0
@mdx-js/react	^1.6.22	^3.0.0
react	^17.0.2	^18.2.0

Dev Dependency	Current	New
@docusaurus/module-type-aliases	^2.4.3	^3.0.0
@docusaurus/theme-common	^2.4.3	^3.0.0
@docusaurus/types	^2.4.3	^3.0.0
@docusaurus/tsconfig	none	^3.0.0
@tsconfig/docusaurus	^2.0.1	removed
@types/react	none	^18.2.36

• @tsconfig/docusaurus does not explicitly support v3, so it has been replaced by @docusaurus/tsconfig. Recommened by Docusaurus v3 documentation: TypeScript Support
• Adding @types/react as this saves some overhead of adding it later when we inevitably use react directly.

Upgrade Guides:

• Upgrading to Docusaurus v3
  • Turn MDX v1 comments compatibility off (default: on)
  • Turn MDX v1 admonitions compatibility off (default: on)
  • Leave MDX v1 headingIds compatibility on (default: on)
• React 18 Upgrade Guide
• Migrating from MDX v1 to v2
• Migrating from MDX v2 to v3

[seanmakesgames]

Build worked correctly. Landing page loaded fine in a codespace.

Thank you for writing up the 'note' at the beginning of the PR. When I saw all the changes and also saw 'using the upgrade policy'; I was like -- no! haha

Just some comments / questions for the settings. Left inline. Probably we want @danswann to take a look at this PR before merging it.