This ticket follows on from a discussion with Jim Bosch about how to deal with SingleFrameMeasurement tests failing config validation because of how the slots and plugins are intended to line up. We added ignoreSlotPluginChecks to BaseMeasurementConfig init, so that those tests wouldn't fail, but Jim pointed out that there is a broader problem of how we need to validate the input vs. expected vs. output catalog schemas against what is going to be run in the task and plugins. We didn't come up with any further solutions, so this ticket is to at document those concerns, note the deprecated "ignore" kwarg listed above, and be a place for exploring how to handle this problem.