feat: Upgrade to bootstrap 5 - #22

What

what the PR changes

• Oh boy where to begin...
• Added a proper README.md with running and setup instructions
• Added a docker-compose.yaml so that the project can be built and run easily
• Removed the HACKING folder and changed to a .env.example with updated env variables
• Added a real header.tmpl for the nav bar and use it across the app
• Updated the UI to use more bootstrap features and be
• A lot of other small changes :P

Why

why these changes were made

I wanted to make some improvements to the functionality of plug but getting it running was a struggle as it was not at all setup for local development.

Test Plan

how did you verify these changes did what you expected

A lot of local testing and asking eboard members to sanity check me.

Env Vars

did you add, remove, or rename any environment variables

• Renamed all of the csh auth env variables to be uppercase to follow conventions.
• Added a S3 bucket env variable S3_BUCKET_NAME to let devs specify the name of their S3 bucket instead of just trying to use the prod one which is plugs.
• Added an LDAP_WRITE_MODE env variable to allow for devs to disable the attempted ldap writes and crashing the backend.

Documentation

did you add or update any documentation. PRs should, at the minimum, update documentation when they make existing documentation out of date.

Made the README.md actually helpful for getting plug setup locally

Checklist

• Tested all changes locally
• Wrote this code wayyyyyy too late at night