Draft version timestamps not updated when embargoed assets were moved

[jwodder]

It appears that, on or around April 29, embargoed asset blobs were moved from the dandiarchive-embargo bucket to the dandiarchive bucket. This was accompanied by updates to the assets' contentUrl metadata, and the assets' modified properties were updated at that time, but the modified properties of the respective Dandisets' draft versions were not updated, and backups2datalad does not like this.

For a specific example, the embargoed Dandiset 000770 contains an asset sub-Elgar/sub-Elgar_ses-2022-06-04_ecephys.nwb with a modified property of 2024-04-29T19:35:05.558024Z, yet the modified property for 000770/draft is still 2024-04-09T19:15:02.126137Z.

[jjnesbitt]

So it seems this is mainly a retroactive issue? That is, we should update these respective versions to reflect the last modified time of those assets, but it's not a systematic issue going forward? Seems like it's just a side effect of the embargo re-design data migration.

[jwodder]

@jjnesbitt Yes, that sounds correct.

[jjnesbitt]

@jwodder I believe I've addressed the issue. Can you verify this?