Change to how CLI Premium license expirations are handled in Wordfence CLI

[ewodrich]

The first year purchases of Premium CLI licenses are approaching expiration and in testing an expired CLI Premium license it was found that most of the subcommands produced either a generic error message or the message Error: License validation failed.

Test results:

• malware-scan and terms fail to run and provides generic error message Error: Request failed
• vuln-scan, remediate, and count-sites fail to run and provide error message Error: License validation failed.
• version, help, and configure are permitted commands with an expired CLI Premium license

Suggested changes:

• when subcommands malware-scan, vuln-scan, or remediate are input, I would suggest we prompt the user that their CLI Premium license has expired and direct them to the CLI web page to renew. We can follow that up with a prompt along the lines of "Would you like to run Wordfence CLI under a free license?" with 'yes' running CLI free and 'no' returning the user to the command line. An alternative option would be to prompt to install WF free, overwriting the expired Premium license.
• with subcommands count-sites and terms, my suggestion is the user should be able to run these commands regardless of the status of the CLI license expiration.
• subcommands version, help, and configure - no change suggested