Implement components and front page

[No767]

Summary

This PR aims to address the need for migrating components to NextUI. The rationale behind it is simple: we are building a website, not a components library. In addition, the PR aims to implement the front landing page of the website.

The components implemented are detailed as such:

• Global Navbar

This PR is incomplete but merging regardless in order to remove an dependency blocker

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

[sonarcloud]

Quality Gate passed

Issues
11 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud