We bumped the LATISS visit region padding on DM-30869, but have no way to update dimension records already in the database (other than dangerous direct-SQL usage).

On this ticket:

• add Registry.replaceDimensionData (should be able to delegate essentially everything to Database.replace);
• add config options to RawIngestTask and DefineVisitsTask that switch them to use this method instead of syncDimensionData;
• run DefineVisitsTask for LATISS in /repo/main to update those regions.

All of these new interfaces need to come with warnings about them being advanced/admin operations that should be only used to fix bad data after careful consideration - e.g. when the visit padding is increased, or we fix something in the metadata translation.