Implement release blocking job criteria

[spiffxp]

This is an umbrella issue for followup work to #346

That PR describes aspirational release blocking job criteria. This issue is intended to track the followup work, including:

• assignment of owners to all jobs
• descriptions added to all release-master-blocking jobs
• propose the creation of sig-foo-alerts@googlegroups.com or reuse of sig-foo-test-failures for all sigs that need to be responsive to test failures
• the creation of the release-informing dashboard, and moving jobs out of release-master-blocking to that dashboard
• a bigquery run that generates metrics for jobs currently on the release-master-blocking dashboard

/sig release
this is sig-release policy
/sig testing
this will be assisted by sig-testing tooling

EDIT 2019-07-23: AFAIK metrics is the only thing that remains to close this out

[jberkus]

Are we consolidating all non-blocking dashboards into -informing?

I'd be in favor of that.

[BenTheElder]

/cc

[spiffxp]

/milestone v1.14

I would like for us to implement this for the v1.14 release