This may take phasing in over time, but we accidentally lost some storage tests. I see this as a fairly low priority

Two benefits:

• people can't just nerf tests instead of fixing them
• when a test gets renamed, forces them to  update the ci-test-mapping

We would need to implement StaffEngineerApprovedObsolete in test mapping (column is there but unused) so we can customize this behavior per test. 

We also need to deal with the problem in 4.13 where some operator state change tests showed up in non-upgrades (that's the reason many squares are dull green in the 4.13->4.14 comparison)