After the validate_base shift, validateDrp.py now requires a filter to be listed in the etc/metrics.yaml in order for it to run. If no match is found, it bails out.
1. validateDrp.py should instead do "something reasonable". Likely this means picking 'r' with a clear message that it is doing so.
2. validateDrp.py should successfully calculate all metrics that it can. Failing on one metric or with the ocnfiguration of same should not lead to crashing:
The spirit of validate_drp is that it should just run on a data repo and produce reasonable input. An additional level is providing specific comparison against LSST SRD-level performance requirements or specific other performance levels.