Merge react-rewrite branch from fork

[No767]

Proposed changes

Move from CRA to Vite, tailwindcss config that works, etc. This also introduces TypeScript, which I may or may not remove later on depending on how annoying the type checker wants to be

The old react branch will not be touched and this is a whole new branch

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 (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• Lint and unit tests pass locally with my changes (Yes, against Node 18 and 20 w/ ESLint and TSC)
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Responsiveness

Check off the different browsers and devices you have tested on. Note: testing includes Horizontal and Vertical alignments

Browsers

• Chrome
• Firefox
• Edge
• Safari
• Brave
• Opera

Devices

Phones

• Moto G4
• Galaxy S5
• Pixel 2
• Pixel 2 XL
• iPhone 5/SE
• iPhone 6/7/8
• iPhone 6/7/8 Plus
• iPhone X

Tablets

• iPad
• iPad Pro

Desktops

• Windows 10
• MacOSX
• Ubuntu

Screenshots

Further comments

The changes and move to Vite have already been discussed and many more