Issues with authentication prompts when using profiles

[traeok]

Describe the bug

There are a few issues with how we prompt for authentication when using profiles. Some issues are exclusive to v3 and others span across both major versions.

• Extenders do not get credential prompting for free when using the APIs outside of Zowe Explorer actions
  • This may not be that problematic, but would be nice for extenders to have, and avoids the need for extenders to add the logic themselves (code duplication)
  • Applies to: v2, v3
• We need to block before attempting to use a profile again with the invalid creds/token, to avoid continued attempts by the filesystem (some out of our control)
  • This is an issue and will need to be resolved to avoid credential loops in virtual workspaces and other areas
  • Applies to: v3
• We have to add error handling everywhere that the APIs are used to handle authentication errors
  • Not a serious issue, but the code duplication can be avoided and will need to be considered for every new feature/fix
  • Applies to: v2, v3
• While its not an issue, it would be nice to "lock" a profile so that we can wait / prompt for auth before making another request
  • Applies to: v2, v3

To Reproduce

Expected behavior

Screenshots

Desktop (please complete the following information):

• OS:
• Zowe Explorer Version:
• (Optional) Zowe CLI Version:
• (Optional) Are you using Secure Credential Store?

Additional context

[github-actions]

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.