Improve activation errors and team config logging

[phaumer]

Proposed changes

The new Zowe configurations files are more error prone and harder to troubleshoot. We need to provide more clear logging and error messages to help users self-diagnose.

I started cleaning up the error message shown when activation runs into issues loading configuration files. I was talking about problems with the logger before. I also started adding more information about the actual profiles found to the readConfigFromDisk(), but that only works when loading a valid file. Looking for more ideas for how to diagnose and invalid file or problems reading the files.

Also moved down the mkdir operations in activation as they were calling error handling which required profiles to be loaded first.

Release Notes

Milestone:

Changelog:

Types of changes

What types of changes does your code introduce to Zowe Explorer?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Updates to Documentation or Tests (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This checklist will be used as reference for both the contributor and the reviewer

• I have read the CONTRIBUTOR GUIDANCE wiki
• PR title follows Conventional Commits Guidelines
• PR Description is included
• gif or screenshot is included if visual changes are made
• yarn workspace vscode-extension-for-zowe vscode:prepublish has been executed
• All checks have passed (DCO, Jenkins and Code Coverage)
• I have added unit test and it is passing
• I have added integration test and it is passing
• There is coverage for the code that I have added
• I have tested it manually and there are no regressions found
• I have added necessary documentation (if appropriate)
• Any PR dependencies have been merged and published (if appropriate)

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

[zFernand0]

The extra logging information is certainly good to have in order to diagnose a problem.
Thanks! 😋

[rudyflores]

Looks good to me as well! Thanks for these helpful changes Peter!