Better error handling+better endpoints for http interface

[yangdanny97]

For a more robust backend API we should implement this stuff (after all the endpoints are converted to python and completely working, please don't start rewriting halfway through):

• standardize endpoint naming, remove redundant endpoints (xbox on and xbox off are different endpoints)

• backend should be able to catch errors and return a response describing what the error is (see below)

• endpoints should return JSON obj in {status: , body: } format, where status is 200 if request was successful and 500 if there is an error that was caught by backend (this is still treated as a successful request but front end can read the status number and handle it that way). body should be some error message string if status is 500, or some JSON obj if status is 200.

• write a documentation sheet for endpoints incl response format and example requests

• write test cases in for backend that simulate requests to the server (ideally the API's should not be manually tested using the GUI, and frontend testing should just be for interface features)