Database logic for notifications

[pshriwise]

Writing this down somewhere so when things break in the future I can be pissed at my past self for being such a fool.

New attributes to add to AUDLclasses.py:

• a global boolean to enable or disable notifications in the database
  This value will be checked any time that a notification is about to be sent. If false, the notification will not be sent
• two boolean values on Game classe (start/end_notification_sent) for if notifications have been sent about that game already
  These values will always be instantiated as false in the Game init method. The updating of these values will be done when a database is being refreshed or started.

When starting the database:

• any upcoming games will be instantiated with false notification values, no notifications will attempt to be sent
• any ongoing games will be set as such and a notification will be attempted but the global notifications value will prevent them from going out
• any over/ulti numbers declared over games will be set as such and a notification will be attempted but the global notifications value will prevent them from going out

When the database/server is running:

• at this point when games are being updated (either due to the refresh interval or by an incoming game update from ultianalytics) notifications will attempt to be sent by the notification handler. If the notification is successful, then the game's start/end notification attribute will be set to True
• When these values are set in future game updates/refreshes the game's attributes will act as a filter for notifications if the game notification has already been sent.

[pshriwise]

This was largely completed last spring. Way to go past pat.