Authorization middlewares and utils

[danielp1218]

Added some middlewares and utils we can use for enforcing role-specific access to certain routes. (e.x. admin-only, or hacker-only routes). Also adapted existing systems to the new system + fixed up some minor dev details.

Specifically:

• Added a requireRoles() middleware to enforce access on a specific route
• Added isUserType() for checking if a request has a certain level of access permissions

[BlazingAsher]

tbh I am not a general fan of mocking so much. I think you should better separate usage of the db and the service functions.

for example, for isUserType, you should have a function called "fetchUser" or something similar that is called inside the function to retrieve the user. Then, using that output, perform logic on it.

that way, you can have an integration test (with a real db) for the fetchUser function, then mock only fetchUser to return users depending on that you're trying to test. this provides a much better separation of concerns and should make the tests way less verbose.

TLDR: I would move DB access outside service functions, so there's a more clear line for where you need a unit vs integration test.

also the route tests I would always make to be an integration test.

[BlazingAsher]

I think it's fine enough. You'll always need a global admin role anyways.

[danielp1218]

for example, for isUserType, you should have a function called "fetchUser" or something similar that is called inside the function to retrieve the user. Then, using that output, perform logic on it.

I already had a queryUserType, I just forgot to update my tests to do them individually...

More generally, our tests are really bloated because doing unit tests on DB access is really annoying and integration testing is not so easy either (bun doesn't support testcontainers which is the only easy way I know 😭). I agree that mocking so much feels really pointless though. Will likely have to fix later, just depends on priorities.