Feature - HTTP Requests - Connecting Client and Server

**Server Changes:**
- Updated server side restful API to handle saving access tokens
- Consolidated all code involving saving data
- Updated database and code interacting with it to handle saving long term access token data
- Added access token verification (check if token was generated by my app and for the correct user) before long term token is generated
- Saving expiration time, time generated and user ID, with long term access token instead of just the token
- Wrote backend code to delete user's access token and saved event IDs from database when user chooses to logout
- Added Not Found 404 status code
- Wrote code for server to handle getting all event data from user and send to client
- Wrote a function for getting user's name and to also test validity of access token - to be called whenever settings are retrieved
- Updated server to return user's name whenever settings are retrieved

**Client Changes:**
- Not sending event data with settings to settings panel anymore - must do separate request (Will try to get on client side first and request to server as las resort - should be faster than always getting through server when getting settings)
- Wrote HTTP function for getting settings for widget and settings panel from server
- Finished HTTP post function for client to save data to server
- Wrote frontend code to make HTTP request to server to delete user info due to logout
- Updated client to accept user's name when settings are retrieved from settings panel
- Wrote HTTP request for client to use when it's not possible to get event data from client side for settings panel