Populating `quotaUser` on requests

The issue tracker is for reporting product deficiencies. How do I questions should be posted to the discussion forum at https://groups.google.com/group/got-your-back. When in doubt, start at the discussion forum and return here only when instructed to do so.

Please confirm the following:
[x] I have upgraded to the latest GYB release from https://github.com/jay0lee/got-your-back/releases and I still have this issue.
[x] I am typing the command as described in the GAM Wiki at https://github.com/jay0lee/got-your-back/wiki

Full steps to reproduce the issue:
1. Configure GYB via a service account
2. Run GYB for multiple users
3. Hit rate limits

Proposed improvement:
According to the [docs](https://cloud.google.com/apis/docs/system-parameters#definitions), all Google APIs support a `quotaUser` parameter to specify the user rate limit bucket to charge requests against. When using a service account to perform exports, this should allow the account to take full advantage of the available rate limit buckets. From a quick review of the GYB source, it doesn't look like this parameter is populated anywhere.

_Assuming my reasoning is correct_ adding this parameter would allow a service account to service more requests before hitting RLs.

No source file or test is named. Start by locating the Python request construction used by service-account exports, then compare it with the Google API quotaUser documentation; done means requests use an appropriate per-user quota bucket and the multi-user rate-limit behavior is verified.

Written by the indexing model from the issue text.