Created skeleton for API endpoints

[amy-lei]

• created skeleton
  • Included docstrings with the parameters to expect
  • Included comments with rough idea of what needs to be done
• untracked server/templates/index.html file

Laid out the skeleton so that anyone can pick up the task of working on the api without having to worry about coordinating with the frontend since the expected params are there.

Untracked index.html because this is a resulting file from npm run build or npm run watch. It's constantly changing, but it's also easily rebuilt if one follows the instructions on how to run the app locally on our README.md.

[ebonnecab]

I separated the authorization stuff into the auth.py file. You can find the routes defined there. all you should need to do is plug in the template and have the form correspond with the schema defined in the SQL file. the user itself is stored in the db.

The other API endpoints look good, we are only missing one for viewing an individual contact and one for deleting a contact. We can go over that in a call though

[amy-lei]

Given that our DB has changed along with the overall structure of the backend, no point in merging this now