Issue Reporter: Support configuring data sent to extensions

[RMacfarlane]

Continuation of #45673

Now that users can choose to file on extensions, extension authors should be able to specify additional data to include in the report. This could potentially include

• User settings
• launch.json information
• Metadata about the workspace (is it multiroot)
• Console errors
• Data specific to the extension

[Almenon]

By default the extension log should definitley be included within the report. Extension settings would also be very helpful.

[rkeithhill]

To add to what @RMacfarlane says, the PowerShell extension would love to supply the PowerShell version info in this issue report. We'd (and I suspect most extension authors) would like to see a list of all loaded extension versions. There is sometimes "interference" between extensions and having this information can help determine if what a user is seeing might be a result of this.

Here is an example of the PowerShell version info and extension info we generate with our extension's bug report command:

PowerShell Information

Name	Value
PSVersion	5.1.17134.137
PSEdition	Desktop
PSCompatibleVersions	1.0 2.0 3.0 4.0 5.0 5.1.17134.137
BuildVersion	10.0.17134.137
CLRVersion	4.0.30319.42000
WSManStackVersion	3.0
PSRemotingProtocolVersion	2.3
SerializationVersion	1.1.0.1

Visual Studio Code Extensions

Visual Studio Code Extensions(Click to Expand)

Extension	Author	Version
cmake	twxs	0.0.17
code-settings-sync	Shan	2.9.2
cpptools	ms-vscode	0.17.6
csharp	ms-vscode	1.15.2
debugger-for-chrome	msjsdiag	4.7.0
EditorConfig	EditorConfig	0.12.4
githistory	donjayamanne	0.4.1
gitlens	eamodio	8.4.1
html-snippets	abusaidm	0.2.1
PowerShell	ms-vscode	1.7.0
sass-indented	robinbentley	1.4.9
theme-cobalt2	wesbos	2.1.6
tslint	eg2	1.0.33
vscode-eslint	dbaeumer	1.4.12

If we had this and there was a way to invoke the issue reporter programmatically, we would redirect bug report command to pop the issue reporter and probably, over time phase out our bug report command in favor of the built-in one.

[rkeithhill]

Oh and we'd like to show them how to attach log files generated by the extension to the bug report e.g.:

Attached Logs

Follow the instructions in the README about capturing and sending logs.

Of course, if the issue reporter supported attachment of log files (or zip of log files) and uploaded that with the bug report - that'd be sweet!!

[rkeithhill]

Extension settings would also be very helpful.

Yes! But we would only need the non-default settings.

[bwateratmsft]

The Docker extension along with several Azure extensions managed by @EricJizbaMSFT and @StephenWeatherford would really benefit from this as well.