Refactor project styling to use TailwindCSS

[digitdustin]

Upgrade styling to use TailwindCSS instead of MUI to:

• Improve developer experience
• Decrease styling bias
• Decrease frustration in avoiding overriding styles
• Allow for upgrade to NextJS13 (MUI currently not supported with server components)

[marcgabe15]

Note: NextJS13 app directory uses server components by default and if we want client components (which our app needs) we'll need to put "use client" on every single file. Our current app right now is hosted just a static files hosted over a cdn so by default we still can't use app directory unless we want to move towards running this on an actual server. Next.js is tightly coupled with Vercel's system so its super opinionated on using SSR.

Some things to think about:

• What is the value add for us to move to SSR vs using CSR right now?

Some advantages I can think of right now:

• Vercel is free! (will it be free forever?)
• SEO/Page ranking

Disadvantages:

• It's easier to set up just some static html/css/js files rather than fully loaded ssr
• TTI (time to interactive) is slower on SSR which in our case our app is more meant to be interactive than read only