Add back md5 to zarr object url signing

[danlamanna]

Related #1494

The MD5 parameter needs to be part of the original signed URL, otherwise S3 will reject the upload URL. This means the MD5 header used by the client is mandatory.

The CLI will need to update the /files step to take a [{path: foo, md5: bar}, ...] structure instead of a plain list of paths.

[jjnesbitt]

@jwodder This will require another update from the CLI

[jwodder]

Will the CLI still need to supply a Content-MD5 header when PUTing file contents?

[danlamanna]

Will the CLI still need to supply a Content-MD5 header when PUTing file contents?

Yes, that's what allows S3 to refuse it at time of upload if it's incorrect.

[jwodder]

PR to CLI: dandi/dandi-cli#1215

[danlamanna]

Merging this side of things first. Please hold off merging the other side until I confirm this is working.

[jwodder]

I tried to use my CLI PR to upload to staging, but it failed with a 403 and the message "The request signature we calculated does not match the signature you provided. Check your key and signing method."

[danlamanna]

Yeah, sorry about this. We're in an unfortunate situation where our local object store behaves differently than S3 in this specific case, so we're developing a bit blind. I'll update when I figure out what's going on.

[dandibot]

🚀 PR was released in v0.3.18 🚀