Studio CLI: Validate access token before starting command operation

[gavande1]

Related issues

• Fixes STU-464

Proposed Changes

This PR addresses the issue of invalid authentication states in Studio. Currently, the CLI uses the access token without first checking if it's still valid or has been revoked. To fix this, the PR adds a step to validate the access token by calling the /me endpoint before starting any CLI process.

Testing Instructions

1. Check out this branch.

2. Start the app:

   npm start  

3. Log in to your WordPress.com account.

4. Build the CLI:

   npm run cli:build  

5. Run the following command to create or list preview sites:

   node dist/cli/main.js preview list --path ~/Studio/[SITE_NAME]  

6. Confirm that it lists existing preview sites. If none exist, create one.

7. Open your appdata-v1.json file, located at: "/Users/[YOUR_USER]/Library/Application Support/Studio/appdata-v1.json"

8. Manually modify the authToken.accessToken value to an invalid token.

9. Run the same CLI command again:

   node dist/cli/main.js preview list --path ~/Studio/[SITE_NAME]  

10. The CLI should now return an authentication required message.

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[epeicher]

Thanks Rahul! I have tested this, and it works as expected. When modifying the token, the CLI returns the error as expected. LGTM!

[fredrikekelund]

Nice improvement 👍