DM-55695: Add psfArea, psfIxx, psfIxy, psfIyy columns to VisitDetector.

[erykoff]

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

[gpdf]

@laurenam should still do the review, of course, but just as a comment:

This is exactly consistent with the new column-schema-referencing style and does not have any effect on the DP2 schema or force it to be "frozen" yet.

[laurenam]

No apdb.yaml‎? Also, they like a news fragment à la 8fc103f to be added.

[laurenam]

Do these really need to be double? (I see psfSigma is float above).

[erykoff]

They are produced as double. If we had any unit tests of these I think they'd show that psfSigma has a mismatch.

I don't know what the plans are here, so I wanted to keep them matched to what was produced.

Fortunately, these are per-detector and not per-object.

[gpdf]

@erykoff Can you give us a one-sentence summary of this change so that we can patch in the (required) news fragment file for the next round of release notes?

"Added per-detector PSF shape metrics to VisitDetector in DRP development schemas" is fine unless you want to be more specific.

#526 is ready to go, you can comment/suggest there if you don't like the summary.