User API Routes

[noahgiboney]

Description
With the addition of non profit accounts, we no longer need the AdminSchema. This would rather be a user model with a role indicating the role of the user. We are also gonna need GET and POST routes for user.

Acceptance Criteria
User Schema is accurate and API routes work correctly.

Steps:

• Refactor the admin schema to be user schema. Include the following properties: name, email, isAdmin (boolean). Delete the password field. This will be for clerk to handle
• Create a new POST route under api/users/route.ts
• Create a new GET user by ID route under 'api/users/[ID]/route.ts]`
• Test API routes to ensure users are in mongo DB