[ENG-335] [OATHPIT] Throw Google Drive into the Oath Pit

[cslzchen]

Ticket

https://openscience.atlassian.net/browse/ENG-335

Purpose

Enable and update the Google Drive provider for aiohttp3.

Changes

• Simply rewrite async with ... as resp: ... into resp = await ....

Side effects

No

QA Notes

Below is a list of what I have tested locally according to the list provided by the ticket. Surprisingly, everything works as expected.

As usual, 1) files tested are of five different sizes: 20B, 1.4MB, 11MB, 88MB and 264MB, 2) intra-move-copy are tested between two components connected to the same Google account, one component is the Drive root and the other is a Drive folder, and 3) no comments indicates a PASS for each item.

• Getting metadata for a file / folder: tested along with file view and folder listing

• Downloading

• Uploading (both to the root and a subfolder

  • One file
  • Multiple files
  • Chunked upload: N / A

• DAZ

• Deletion

  • One file
  • Multiple files
  • One folder
  • Multiple folders

• Folder

  • Creation
  • Upload to folder: tested along with Uploading
  • Deletion: tested along with Deletion

• Rename

  • One file
  • One folder

• Verifying non-root folder access for id-based folders: N / A

• Intra move/copy

  • Move
  • A single file, a single folder, multiple files and multiple folders between the same Google Drive account connected to two different components have been tested.
  • Confirmed from server logs that there was no celery task triggered for all intra-moves
  • Copy
    • A single file and multiple files: similar as intra-move, there was no celery task triggered
    • A single folder and multiple folders: celery tasks were triggered, which indicates inter-copy have been used instead

• Inter move/copy (light testing only)

  • Move and Copy
  • A single file, single folder, multiple files and multiple folders are tested
  • Bidirectional between Google Drive and OSF Storage

• Comments persist with moves (light testing only)

• Revisions: enabled and tested

• Project root is storage root vs. a subfolder: N / A but tested anyway given I need two components for testing intra-move-and-copy

• Updating a file: tested along with Revisions

Deployment Notes

No

[coveralls]

Coverage increased (+4.8%) to 74.131% when pulling 11299f8b629f5686e9c6c907ff81e85bd8eaf5cd on cslzchen:feature/oathpit-google-drive into be3b81f989cdb44de0b213635bd9073351297cf5 on CenterForOpenScience:feature/oathpit.

[cslzchen]

As discussed in person, the new test failures caused by base image update merged will be / has been fixed along with CR by @felliott . Given that I have rebased the PR, we may need to manually commit-close this PR during merge.