Initial test of an alert applies a 30 second timeout rather than configured timeout

[mcoles]

When a user subscribes to a View on an Alert schedule, the first time VizAlerts tests it on the schedule, the timeout value used is 30 seconds. This can cause problems for longer running views, and is especially unhelpful when the alert is to be run daily or weekly, as these can be alotted longer timeouts than normal, and the subscriber will need to go longer with no good information from their initial alert.

The fix should probably be to derive a fake "last ran at" time from the schedules table in the PostgreSQL repository, which would provide a more-valid value to apply the timeout rules by. For example, for an alert that runs daily, but has never run before, we can provide now() minus 24 hours as the last_ran_at time, which would cause it to use a rule matching 86400 seconds, instead of 1800 (30 minutes). That'd allow it a 5 minute timeout under the default config, instead of 30 seconds.

[mcoles]

Added into bug fixes branch, will integrate from there into dev, then master. Closing issue!