[Backlog idea] Diagnostics panel/non-intrusive notifications for the Brackets core and extensions to use

[busykai]

Inspired by discussion in #6442. Went through the Trello and the closest if found was this: diagnostics report, but rather different use case.

Sometimes Brackets core or extensions may experience a problem that could be diagnosed without failing and report to the end user. For example, JSHint extension could be supplied a malformed configuration file and fall back to the default settings. User has to be notified that the issue occurred, but has been mitigated. A lot of such diagnostics goes into the console today. However, to access the console a Brackets user (with development background or not) have to start a debugging session.

As Brackets stabilizes, more and more casual users will be using it and it would be extremely helpful to have:

1. Non-intrusive notifications (e.g. slide in, slide out) for the diagnostic messages.
2. An analog of console directly available for viewing from the UI instead of using CDT where these diagnostic messages get stacked.

This would help guided troubleshooting when possible (when the code is intelligent enough).

[pthiess]

move to backlog

[njx]

Another thought on this...it might actually make sense (in addition or instead of this) to have a way to capture the entire normal console log in Brackets for diagnostic purposes.