Make auth refresh more convenient with secure storage

[samcoe]

This PR adds some convenience functionality to auth refresh command. Now if a user logged in with auth login --secure-storage or auth refresh --secure-storage next time they use auth refresh the --secure-storage flag will be implicitly set. Basically, if the token we want to refresh is coming from secure storage we assume that the user wants to continue to use secure storage even if they forgot to add the --secure-storage flag.

[mislav]

This looks good; thanks.

Would we also consider supporting explicitly disabling via --secure-storage=false to quit storing in keyring and write the token to config file instead?

[samcoe]

@mislav I wasn't not planning on supporting that flow. If the user wants to quit storing the token in the keyring using auth logout and then auth login would be the recommended path. I can see the value of just being able to do it in auth refresh but with the release looming I would suggest we hold off and perhaps add it before the next release.