Improving transfer tool to list files in Wasabi and AWS S3 backup bucket directory to show curators that files have been transferred.

[rija]

User story

As a curator
I want to know what is going to be copied by the transfer tool when its run in dry-run mode
So that I can see if its doing whats expected

acceptance criteria

given a curator needs to update a dataset that no-longer has an active userbox associated with it
when the curator puts the additional files in a new userbox
then they can run the transfer script, or something similar, to transfer those files to the relevant dataset DOI area in Wasabi (and S3 backup)

given above
when the curator runs the transfer (or other) script
then the files in the new userbox get copied to the wasabi server
and the DOI.md5 and DOI.filesizes and readme_DOI.txt files all get updated to include the new files
and the relevant file details are updated in the database
and (assuming its a published dataset) the dataset history log is updated with an entry to describe the new additions to the dataset

OR there are instructions of what the curator must do to ensure those files are correctly updated.

additional information

In some cases I need to make updates to some files in published datasets, e.g. the work Bastien has been doing with the 3d images, or when someone spots a mistake in a file.

Overlap with ticket #2200

@rija said "whats this ticket for?"
@only1chunts replies "I've added a user story that I think it relevant"