Move react code to the root of the repo

[No767]

Summary

In order to simplify development, the old react directory now has all of the stuff moved into the root of the repo. This makes it a lot easier to develop and pick up. One of the main rationales is that you can just run npm install --save-dev in the root after you clone instead of knowing to cd into the react directory.

Second, we don't have multiple conflicting frameworks (see master branch for an idea of that), and there is really no use to have all of the code stored into a directory instead. React will and moving forwards, will still the framework that is used by this website.

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.
• All workflows pass with my new changes
• This PR does not address a duplicate issue or PR

[netlify]

❌ Deploy Preview for ucmacm failed.

Name	Link
🔨 Latest commit	214239e
🔍 Latest deploy log	https://app.netlify.com/sites/ucmacm/deploys/6769cbc0030a6b000841f653

[sonarqubecloud]

Quality Gate failed

Failed conditions
1 Security Hotspot

See analysis details on SonarQube Cloud