DM-33150 removed Gen 2 support from ap_verify; for the datasets, this entailed backing the dataset contents with a Gen 3 repository rather than uningested files, but (for stability) no other changes.

The ap_verify datasets have historically kept their dataset-specific configuration in Python config files, to ensure that the same configs are being used in Gen 2 and Gen 3. However, this arrangement has prevented use of some Gen 3 features (in particular, pipeline parameters) that let us centralize config information, which in turn has meant frequent updates to the ap_verify dataset configs for changes made to the ApVerify or ApPipe pipelines themselves.

Now that we only need to support Gen 3, there is no benefit to keeping the config files around. Merge all config information into the pipelines that use them, maximizing use of parameters.