Allow DC metadata to be entered in transfer, persist to ingest

These commits allow DC metadata to be entered in the transfer phase. This is implemented by adding a new DC form, which exists in the transfer phase, and saving the metadata to disk in between transfer and ingest.

To save and load DC metadata, the data is serialized to disk as JSON at the very end of a transfer using the new `saveDublinCore` microservice. This happens after the user selects to create a SIP, so it's unlikely that users would be able to try to manually edit metadata after it runs.

At the very beginning of ingest, immediately after the SIP is verified, the new `loadDublinCore` microservice looks for a `metadata/dc.json` file inside the SIP; if present, it populates the DC metadata for the SIP in the database using that file. This allows the DC metadata to be editable by hand during ingest, and makes sure it will be used in the final AIP METS.

To support this, this now persists the contents of the transfer's `metadata/` directory when creating a SIP. In the past, anything there would be discarded when creating a single SIP.

This PR's commit history is still p. messy, will get cleaned up on merge.