Task events metrics for scheduler

[jpbruinsslot]

** Show the user what resources a specific tool has consumed. This would cover all historical data, but is incidental and does not suffer from scalability issue as much.
** Calculate what a proposed Job is likely to consume based on 'recent similar jobs'. This means that we don't need all the data, just a most recent set. Maybe we can have a daily job that trims this materialized view into a two week or N items window to keep the math required for this calculation reasonable?

• If we introduce blob fields, lets stick to something postgres has querying tools for, like json/jsonb.

Originally posted by @underdarknl in #1956 (comment)