Search folders in batches to avoid 413 entity too large from drive api

[tarekrached]

Description of Change

What it says on the tin - search folders in batches to avoid 413 entity too large from the Google Drive API.

Related Issue

Resolves #59

Motivation and Context

When we call drive.files.list() in fullSearch(), we pass all of the folderIds (if driveType === 'team'). When you have a lot of folders, the call to drive.files.list() returns 413 Entity too large because the query is too big.

In this PR I added a MAX_FOLDERS_TO_SEARCH parameter, and batched the folderIds to search into batches of that size or fewer, and then I search over the batches sequentially.

FWIW, we could search the batches simultaneously with a Promise.all().

In my testing with a 4-character search string, 128 folders worked, but 129 folders triggered the 413. Because the querystring contains other data besides the parents, you may hit the 418 with fewer folders, so I set MAX_FOLDERS_TO_SEARCH to 100 to give us some headroom.

Checklist

• Ran npm run lint and updated code style accordingly
• npm run test passes
• PR has a description and all contributors/stakeholder are noted/cc'ed
• tests are updated and/or added to cover new code
• relevant documentation is changed and/or added
  • no user-facing changes

[tarekrached]

I ended up implementing the concurrent searching over the batches of folderIds