Restful server

[arades79]

Summary

Nearly all server URL rules have been changes, and their logic refactored in a way that makes the resulting API relatively RESTful. HTTP methods are better leveraged and more clear, and the endpoints have been simplified. General capabilities were also enhanced that will allow for easier extensibility in the future without requiring breaking changes. All endpoints now speak in JSON, and most web/HTML elements have been removed. These changes should result in a much more scalable server, as well as an easier starting point to develop alternate clients.

Checklist

• [x] If code changes were made then they have been tested.
• [ ] This PR fixes an issue.
• [x] This PR adds something new (e.g. new method or parameters).
• [x] This PR is a breaking change (e.g. methods or parameters removed/renamed)
• [ ] This PR is not a code change (e.g. documentation, README, ...)

[arades79]

The server currently runs and works as expected for methods tested, but the client is still using the old server design, making this change unsuitable to merge to develop until the changes for the client are also ready. Hence this is targeting another branch.

[arades79]

I think it actually makes more sense for chat to be attached to the user endpoints, e.g. /counselors//chat, then instead of having a module level chats dict, chat can just be a member of each user like counselors[user_id]["chat"]