Pinging the user who made the last revision on bounds failures

[bergmark]

This was @hvr's idea

Ideally it should never be needed, but since accidents happen...

Pinging the user who made the last revision to a package will notify them so that they can take responsibility if applicable. The primary use case is for trustees, but giving the revisor's name could be useful information regardless of who made the revision.

The 01-index.tar contains the hackage user name for revisions. We could have a partial map from hackage user name -> github name to send notifications, or just display the hackage user name if a name is missing.

[DanBurton]

I'd say if trustees don't mind being notified in this way, then by all means let's do it. We should perhaps also have an opt-out list for those who do not wish to be notified. (Or perhaps instead, an explicit opt-in for those that do?).

Printing the hackage user name should be harmless in terms of notifications and is potentially useful, so let's definitely do that.

[bergmark]

This partial map would effectively be an opt-in mechanism.