Detect and alert users on unusual subscription run patterns

[danielcompton]

There are some subscription run patterns that are unusual, and that we should alert the user about.

• Show a listing of the full pattern when expanding the sub (truncated to three)
• Show a warning icon if there is a problem in the header
• Print the warning explanation when expanding the sub

[mike-thompson-day8]

Aberrant patterns:

1. a layer 3 subscription which ran but result tests = to last time
2. a subscription which was both created and destroyed within the one epoch
3. destroyed and run in same epoch?
4. created but not run in an epoch
5. Run multiple times in one epoch

[danielcompton]

A subscription that was destroyed and then run intra-epoch is bad news also, indicates that it is being dereffed inappropriately, possibly in an on-click handler.