Improve logging and potential output view to better support end users

[lauren-li]

Is your feature request related to a problem? Please describe. If a user encounters an issue with Zowe Explorer, it is not always clear how to access the logs to troubleshoot the issue, and the log does not always contain the necessary information.

Describe the solution you'd like

• Add more detailed logging at appropriate points in Zowe Explorer to facilitate the user’s troubleshooting experience.
• Consider adding an Output view so users can easily access information/errors/warnings while using Zowe Explorer in the IDE.

Describe alternatives you've considered Current workaround: Users can view pop-up error/info/warning messages from Zowe Explorer. However, if the user needs to refer back to the information later (either after the messages time out or the user has closed them), or the user encounters an issue with Zowe Explorer, then they have to find out where the logs are, and then go navigate to the log files in hopes that the information they need (e.g. for troubleshooting) is recorded there.

Additional context An Output view with improved logging across Zowe Explorer would make accessing this information a simpler task for users. The Output view could also tell users where the Zowe Explorer logs are kept.

[JillieBeanSim]

Rules for exposing user info (privacy related) Rules for log messages for developers (error, info, warn)

[JillieBeanSim]

setting log levels for Zowe Explorer use Env Var as default if exists