Entirely rewrite documentation

[No767]

Summary

From Sphinx to Docusaurus... The documentation has been now written using Docusaurus to ensure that it can be extensible for other SIGs/projects and documentation for the website can stay fresh. This time, it's also deployed on Netlify.

Caution

This breaks the old docs, but the old docs still can be viewed using the old link.

Types of changes

What types of changes does your code introduce to the UC Merced's ACM Chapter Website?
Put an x in the boxes that apply

• Bugfix (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)
• Documentation Update (Updates to README.md, the documentation, etc)
• Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply

• If code changes were made then they have been tested.
  • I have updated the documentation to reflect the changes. (if appropriate)
• Lint, format, and unit test workflows pass with my new changes
• This PR does not address a duplicate issue or PR

[netlify]

✅ Deploy Preview for ucmacm canceled.

Name	Link
🔨 Latest commit	793d645
🔍 Latest deploy log	https://app.netlify.com/sites/ucmacm/deploys/66d95d99a20da00008de7b4a

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud