Summary:
Here is the current plan:
- Update GetAugmentedToken to take an additional API key field. Now, users can either specify a token (normal workflow) or API key (new workflow) to get the augmented token. The change to the proto is in this diff.
- In followup diff(s): Update GetAugmentedToken to use the APIKey, match it to a user, and create an augmented token for that user.

Alternatives:
- We can add a separate GetAugmentedTokenfromAPIKey rpc call if we want to separate these two flows more

Test Plan: n/a

Reviewers: zasgar, #engineering

Reviewed By: zasgar, #engineering

Differential Revision: https://phab.corp.pixielabs.ai/D6957

GitOrigin-RevId: b3bb00872339bacc81dcd2bab5a3d417627c7350