[CHE-167] BE Refactor Error Handling

[seantokuzo]

Description

**This PR requires a rebuild of the development image. codehammers/ch-dev-dep-v3 does not currently include express-async-errors dependency

What it do:

• Creates reusable custom error classes for throwing common errors
• Adds express-async-errors package for easy error catching in async middlewares
• Refactors the global error handler to handle custom errors
• Refactors catch all route handler to use custom NotFoundError error class
• Separates express app config logic from server startup logic
• Adds environment variable checks before server startup
• Adds necessary development env vars to docker-compose-dev.yml
• Makes connectDB more extensible by accepting connection string as arg
• Refactors auth protect middleware to use new error handling
• Adds optional user property to express's Request interface to handle type errors in protected routes when trying to access req.user and deletes CustomRequest interface and usage of it
• Refactors authController at endpoint /api/auth/validate-session to use refactored protect middleware
• Simplifies usage of protect middleware in all routers
• Simplifies imports of routers from /routes folder
• Updates any tests affected by refactored error handling
• Apparently updates github workflow to use latest dev image which doesn't matter because the workflow builds the image itself

Jira Task

JIRA TICKET

Testing Instructions

To test you will need to build the codehammers/ch-dev-dep-v3 image locally to include the express-async-errors dependency:

• run npm run docker-remove-all
• run docker build -f Dockerfile-dev -t codehammers/ch-dev-dep-v3 .
• run npm run docker-build-check to make sure linting and unit tests pass
• add - 3000:3000 to the ports array in docker-compose-dev.yml to expose the server for manual testing
• run npm run docker-dev
• navigate to a non-existent route, eg. http://localhost:3000/non-existent-route
• should see the response [{ "message": "Not Found" }] in the browser
• should see the ❌ NotFoundError in your terminal with the error's stack trace pointing to app.ts

All Team Members

• I added a descriptive title to this PR.
• I filled out the Description, Jira Task, and Testing Instructions sections above.
• I added or updated [Jest unit tests]for any changes to components, server-side controllers, etc.
• I ran npm run docker-build-check in my local environment to check that this PR passes all linting and unit tests.
• I did a quick check to make sure my code changes follow the recommended style guide.

[brok3turtl3]

Glad to see this all come together. 🎉 Nice work!

Im not sure the applications router flow got hooked up. As well there is some odd image behavior at the moment. Possibly fixed in your database seeder ticket?

[brok3turtl3]

Left a comment regarding applications router and images.

[brok3turtl3]

Hey @seantokuzo ! I noticed

this code has been removed during your re-org. We will need it reintroduced as it is crucial to the production environment. Our AWS deployment pings this route as part of its monitoring system.