Email notification move

[coilysiren]

EmailNotification started in delivery and was eventually moved to notification. This change was definitely needed, but has the potential to cause a variety of issues. The first one I ran into is that if you are doing all of the following:

• using a multi-database setup
• using django's router reccomendations
• routing based on app name
• are storing delivery and notification in separate databases

when you create new apps notification.EmailNotification won't be created properly because it's created by creating a delivery_emailnotification table and then changing that table to notification_emailnotification.

[coilysiren]

There's a variety of solutions to this for end users, including

• allowing both notification and delivery to be migrated on the database that contains EmailNotification
• routing based on both model name and app name, and allowing EmailNotification to be migrated in its target db, in addition to notification

A solution on callisto-core's end would be to rewrite the currently existing to a might more straightforward table creation operation for EmailNotification