DM-33942: Support schema changes for exposure/visit

[timj]

Depends on lsst/astro_metadata_translator#55 and lsst/daf_butler#674

Checklist

• ran Jenkins
• added a release note for user-visible changes to doc/changes

[timj]

Clarification from slack regarding define-visits:

• Remove option for by-metadata and one-to-one visit definition. Always define both now (although the code still has to work with older registry).
• If a visit is a single snap it will have the visitId be the exposureID and will be in both by-metadata and one-to-one visit systems.
• For a multi-snap visit with by-metadata grouping the visitId will be the exposure ID of the first exposure in the visit. It will not be associated with a one-to-one visit definition.
• The second snap in a visit will be associated with a one-to-one visit using the exposure ID as visit ID, and will not be associated with a by-metadata visit.
• In one-to-one mode the first snap in a multi-snap visit will be assigned a distinct visitID that is not the exposureID. This follows the policy of the default visit policy using the most natural visit ID. Since this is a one-to-one visit the visitId must only be defined from that exposure. Simplest would be to add an extra 0 to the end of the exposure ID, and also append something like '_multi' to the exposure's obsId when calculating the visit name.

If a multi-snap visit is missing one of the exposure records (generally expected to be the second one) it should be treated as a multi-snap visit even though the exposure_time and average az/el will be incorrect. Facility must be included to recalculate the multi-snap visit definition when/if the second exposure arrives.