token.json: keep track of which app instance a token was requested for

[DavidS-ovm]

Currently the token.json only stores a single token and switching between --app instances requires deleting the file.

The CLI should instead keep track of the instance the token came from when storing it in token.json to make switching frictionless.

[tphoney]

@dylanratcliffe @DavidS-ovm so i have been playing with this and i have a couple of issues.

multiple auth prompts

I run the 'explore command' i will be asked to authenticate, run through the rest of the command all is 👍.
Then if i run the 'query commmand' i will be asked to reauthenticate. This is because the scopes are different this sucks in terms of expected UX.
made the team aware of this, no easy fix for now. leave it on the back burner

duplicate code in gateway

we re-use the authentication code in gateway for the assistant cli, this is dev only. but it will break when we update anything to do with the token.json file
this is fine, i will copy pasta the code and leave a warning in gateway and the cli for readlocaltokenfile

what do you guys think ?
answered at standup