Large Bulkrax export zipfiles don't open

[lsat12357]

Descriptive summary

Appears to be a problem when a user tries to export the content files with the metadata, and the size reaches > 4G. On the server, the zipfiles are located at tmp/shared/exports; testing the zip with unzip -t shows the error "bad zipfile offset." Kevin notes that the download available from the collection page (same content) works fine though; the code behind this service is here https://github.com/OregonDigital/OD2/blob/master/app/services/oregon_digital/collection_streamer.rb and here https://github.com/OregonDigital/OD2/blob/master/app/services/concerns/oregon_digital/streaming_download_behavior.rb. Is it possible to reuse this code to replace whatever bulkrax does?
The other option would be to break the zipfile into smaller packages; Bulkrax does this based on number of files, but not file size.

Expected behavior

Bulkrax users can export metadata and content files with total package size exceeding 4G

Related work

Link to related tickets or prior related work here.

Accessibility Concerns

Add any information here to indicate any known or suspected accessibility issues for this ticket

[lsat12357]

at the rubyzip site, another user reported the same issue, and acknowledged that the advice "When zipping large files with rubyzip you need to turn on Zip64 support: Zip.write_zip64_support = true." did help for zipfile size < 20GB. Zip64 support is available with rubyzip v.3; we are currently on v.2.3.2 (version 3 requires Ruby 3.0, we are on 2.5.5)
rubyzip/rubyzip#348

[lsat12357]

Update: it looks like we are actually up to ruby v.3.2.1 now, so we could probably try upgrading rubyzip to v. 3 and enable zip64