Match new Jupiter / Light AIP 2.0 specs

This is related to the issue described in the Jupiter Issue Tracker here: https://github.com/ualbertalib/jupiter/issues/354

TODO:

[ ] Main object: Source: $FEDORA_URL/rest/prod/$OBJECT_UUID Destination: objects/metadata/object_metadata.n3
[ ] Fileset metadata: Source: $FEDORA_URL/rest/prod/$FILESET_UUID Destination: objects/metadata/files_metadata/$FILESET_UUID/fileset_metadata.n3 Note: need to figure out how to locate filesets (via proxy objects, or via Solr?)
[ ] Main/Original file in Fileset metadata: Source: ??? Destination: objects/metadata/files_metadata/$FILESET_UUID/original_file_metadata.n3 Notes: The main file has type pcdm:OriginalFile
[ ] File content (e.g. PDF files): Source: $FEDORA_URL/rest/prod/$FILESET_UUID/files/$ORIGINAL_FILENAME Destination: objects/files/$FILESET_UUID/$ORIGINAL_FILENAME Note: filename is in contained_filename in fileset_metadata.n3
[ ] Characterization (PREMIS) log: Source: $FEDORA_URL/rest/prod/$FILESET_UUID/files/$ORIGINAL_FILENAME/characterization Destination: logs/files_log/$FILESET_UUID/content_characterization.xml
[ ] Fixity report: Source: $FEDORA_URL/rest/prod/$FILESET_UUID/files/$ORIGINAL_FILENAME/fcr:fixity Destination: logs/files_log/$FILESET_UUID/content_fixity_report.n3

[ ] Replace owner ids in the metadata with email addresses. This increases complexity of the app since the email addresses are stored in Jupiter's PostgreSQL database. #141
[ ] A method for documenting the order of files needs to be devised. METS has been proposed: https://www.loc.gov/standards/mets/METSOverview.v2.html#structmap
[ ] bagit metadata should be updated for the version of the AIP spec lightaip-2.0
[ ] Update logging to ensure it includes the following information: object identifier, object bag's checksum, file sizes of the original files in the bag, file types of the original files in the bag