Forge ready for use case testing

[quinnwai]

Description

With the large amount of Git DRS changes made, we need to update Forge's dependencies and get it ready to test for main use cases

(spin off of #2)

Main Use Cases

• files, no metadata (forge only)
  • Test with: multi-file e2e test similar to git drs e2e test
  • User does: forge init, git add/commit/push, and forge publish
  • Expected output: All files on Explorer, indexed, and downloadable
• no files, metadata only (forge only):
  • Test with: SMMART
  • User does: forge init, git add/commit/push, and forge publish
  • Expected output: Able to see all files, no indexd records, no downloads
• s3 files, no metadata (git drs + forge):
  • Test with: multi-file e2e test similar to git drs e2e add-url test
  • User does: ???
  • Expected output: All files on Explorer, indexed, and downloadable
• s3 files, metadata (git drs + forge publish): Take existing add-url data, push, then forge publish
  • Expected behavior: explorer should be able to see all files, all metadata, and do file actions (download file / view image)
• empty project: Able to empty project using forge empty
  • Expected output: No project on Explorer, files still indexed and downloadable

[quinnwai]

@matthewpeterkort when you start working on Forge again can you assign this to yourself and move this to in progress? (see board here on doing so)