What does this PR do?

• Remove unused/commented code
• Add comments explaining any complex code
• Add error-handling and catch-alls
• Add defensive null checks
• Remove entire frontend and assets (unless needed @DexterStorey?)

Fixes # (issue)

n/a

Requirement/Documentation

n/a

Type of change

• Chore (refactoring code, technical debt, workflow improvements)

How should this be tested?

[WIP]

• Are there environment variables that should be set?
• What are the minimal test data to have?
• What is expected (happy path) to have (input and output)?
• Any other important info that could help to test that PR

Mandatory Tasks

• Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.

Checklist

• I haven't read the contributing guide
• My code doesn't follow the style guidelines of this project
• I haven't commented my code, particularly in hard-to-understand areas
• I haven't checked if my PR needs changes to the documentation
• I haven't checked if my changes generate no new warnings
• I haven't added tests that prove my fix is effective or that my feature works
• I haven't checked if new and existing unit tests pass locally with my changes