Zowe Explorer should not fail to activate if there is invalid team config

[kristinochka]

Zowe Explorer fails to activate if global or project team config profile is invalid.

To Reproduce

1. Use Zowe Explorer menu to create a team config profile
2. Make edits so that the profile is invalid, for example, invalid JSON format
3. Re-load Zowe Explorer

Expected:
Zowe Explorer to show one message that profile is invalid and allow user to open and fix using Zowe Explorer UI.

Actual:
Numerous error messages all related to Zowe Explorer and Imperative trying to load invalid file and eventually extension not activating.

Screenshots
on Mac:

In Eclipse Che:

Desktop (please complete the following information):

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

Additional context

I suggest there should be 1 Imperative function to check profile validity. If config is invalid inform user and allow to fix, otherwise load the config. In both cases extension should activate.
Currently Zowe Explorer tries loading invalid config and fails in multiple places with many error messages.

[github-actions]

Thank you for creating a bug report. If you haven't already, please ensure you have provided steps to reproduce it and as much context as possible.