save access & refresh tokens and reuse them on next run

If someone is running the tool multiple times repeatedly - probably won't in normal use, but might when first testing things - they might possibly run into the createSession rate limit, which IIRC takes a while to reset. Ideally the app should save the tokens to some JSON file like the mapping, and load them and reuse & refresh them instead of logging in with the password.