suggestion: cli should store oauth tokens

currently every deploy that I'm making of this form:

wispctl deploy -p dist/ -s atvouch.dev

asks both for:

1. handle for deployment
2. full oauth flow for my handle

I can see there's a --store <path> argument to wispctl deploy, but it may be more useful to keep state somewhere else automatically e.g ~/.config/wispctl/state.sqlite? could key handles by the current directory so you could login to multiple accounts on separate folders for their respective deployments

this is not required as part of this suggestion, but if the oauth tokens made by wispctl could be a full superset of all the operations wispctl needs (all the records needing to be read/written) that would be an UX boost since people wouldn't have to continuously re-login