DM-53254: Support forcing DRP association outputs to conform to sdm_schemas

[isullivan]

Checklist

When making changes to YAML files in the schemas directory:

• If applicable, incremented the schema version number, following the guidelines in the contribution guide
• Referred to the documentation on specific schemas for additional versioning information, change constraints, or tasks that may need to be performed, based on which schema is being updated
• Ran Jenkins
• Added a news fragment describing the changes

[JeremyMcCormick]

@isullivan Please do not add back the @id fields. They should not be needed going forward.

[JeremyMcCormick]

Remove these extra spaces in the description.

[JeremyMcCormick]

Remove all @id field additions - they are not needed can be generated automatically (see dp1).

[andy-slac]

Looking at the current data in production APDB I see that many records have *_psfFluxNdata fields as NULL. I guess pipelines currently do not set it to 0 when there are no detections in a corresponding band?
Also note that Cassandra does not support NOT NULL columns, but this could be a problem for SQL backend.

[isullivan]

This change came up because we found (in DRP) that these columns were getting set with NaNs and turned into floats. My code will now set any non-nullable columns with values of NaN to 0 instead.

[andy-slac]

I guess we will also need to update existing data to replace NULLs with 0 in those columns? This should be ~trivial for SQL, but not so much for Cassandra. Version number at the top of the file needs to be incremented, please update it to "9.1.1".

[ctslater]

Looks good from the DRP side, if it's also ok for APDB. I could see leaving mpc_orbits unchanged if you want; since we're not generating that table, nulls aren't going to cause the same problems (and I don't know if their data might have nulls encoded in some way).

[isullivan]

Looks good from the DRP side, if it's also ok for APDB. I could see leaving mpc_orbits unchanged if you want; since we're not generating that table, nulls aren't going to cause the same problems (and I don't know if their data might have nulls encoded in some way).

Good point, I'll drop the mpc_orbits changes.