Token is not properly invalidated when using a custom SSH key.

[FleetAdmiralButter]

Describe the bug
The Lagoon CLI continues to authenticate using the already cached token even when a custom SSH key is specified using the --ssh-key flag.

To Reproduce
Steps to reproduce the behavior:

1. Run any command that interacts with the Lagoon API so that a token is retrieved and cached.
2. Confirm the current user using whoami.
3. Run whoami again, but with the --ssh-key flag pointing to a private key associated with a different Lagoon account.

Expected behavior
The details of the account associated with the SSH key passed in is returned. Instead, the cached token is used to authenticate, returning incorrect account details.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: macOS