Feature/user login

[noahdurbin]

Description of Changes

• added a path for user to login
• configured session store and cors for localhost:3000
• error handling for user login

What are the relevant tickets (if any)

Closes #2

Testing

• Happy path
• user does not exist
• incorrect password

Checklist

• [X] The code follows the project's coding standards.
• [X] Unit tests have been added or updated to cover the changes.
• [ ] Documentation has been updated to reflect the changes (if applicable).
• [X] The code compiles without errors.
• [X] The changes have been tested locally and pass all relevant tests.
• [X] All new and existing tests pass.
• [ ] The pull request has been reviewed by at least one other contributor.

Reviewer Instructions

• Error handling for this endpoint should return the same error messaging

Deployment Notes

• currently cors is only set up to accept requests from local host 3000, was thinking we could set up dotenv files to take care of each environment maybe

[jdmchugh111]

There's some things I have questions about - I think some of it wasn't new code, just code that was commented back in. Overall looks good, just want to clarify some of the config and bin file adjustments I haven't seen before. Also, I think there should be a fix for allowing cors to work on a different port than 3000. If it's easier we might be able to configure frontend to run their development servers on a different port than 3000, but I'm not sure which is an easier fix

Also, you should update the README documentation with the new endpoints/json contracts when you get the chance so frontend can utilize