#765 remove empty css files

[RChandler234]

Changes

Removed Empty CSS files

Test Cases

Smoke test to make sure that nothing in the application is broken/ looks weird

Checklist

It can be helpful to check the Checks and Files changed tabs. Please review the contributor guide and reach out to your squad if anything is unclear. Please request reviewers and ping on slack only after you've gone through this whole checklist.

• [x] All commits are tagged with the ticket number
• [x] No linting errors
• [x] No newline at end of file warnings
• [x] All code follows repository-configured prettier formatting
• [x] No merge conflicts
• [x] All checks passing
• [x] Screenshots of UI changes (if applicable)
• [x] Remove any not-applicable sections
• [x] Assign the PR to yourself
• [x] PR is linked to the ticket
• [x] No package-lock.json changes (unless dependencies have changed)
• [ ] Request reviewers & ping on Slack

Closes # (issue #)

[anthonybernardi]

Nothing better than a PR that looks like this:

[RChandler234]

I couldn't move all the css over, some was too complex to put into a jsx object; I suggest we make a stylesheets folder for the frontend and move the remaining ones there for now and try to find a more consistent way to handle having css in a tsx file (there are ways, but it'd involved adding more packages/ bigger changes, so I don't wanna do it rn); that or if this way looks too inconsistent lmk, and we can just do removing the unused stylesheets for this MR and handle moving the CSS in another one. @jamescd18 @anthonybernardi

[jamescd18]

I see nothing wrong with only have a few components have CSS files, I don't think there's any need to make them be in a separate folder.