Following the merging of DM-30061, ap.association.TransformDiaSourceCatalogTask produces metadata prefixed by "diaSourceSchema" (the first connection) rather than the previous "transformDiaSourceCatalog" (the default name) or the desired "transformDiaSrcCat" (the label in the AP pipeline). I have confirmed that the name argument to the task constructor is faithfully propagated, so the problem must lie farther upstream, possibly in TaskDef. Fix and add suitable tests.

The same issue does not appear with ap.association.DiaPipelineTask. The problem is not caused by the task label being different from the task's default name; I suspect it is related to the presence or absence of init-inputs.