`Terminal Gpu Acceleration` setting `auto` should pick up the `--disable-gpu` command line option

[weinand]

When disabling the GPU on Raspberry PI by running VS Code with the --disable-gpu command line option, I still see rendering issues in VS Code's integrated Terminal. These issues are fixed by turning off VS Code's Terminal Gpu Acceleration setting.

I would expect that the default Terminal Gpu Acceleration setting auto automatically picks up the --disable-gpu command line option in this case.

[Tyriar]

To action this we need to get the GPU status and check that when applying the GPU renderers here:

vscode/src/vs/workbench/contrib/terminal/browser/xterm/xtermTerminal.ts

Lines 426 to 432 in 6fb7d0a

	private _shouldLoadWebgl(): boolean {
	return !isSafari && (this._configHelper.config.gpuAcceleration === 'auto' && XtermTerminal._suggestedRendererType === undefined) || this._configHelper.config.gpuAcceleration === 'on';
	}
	private _shouldLoadCanvas(): boolean {
	return (this._configHelper.config.gpuAcceleration === 'auto' && (XtermTerminal._suggestedRendererType === undefined || XtermTerminal._suggestedRendererType === 'canvas')) || this._configHelper.config.gpuAcceleration === 'canvas';
	}

GPU status is currently used in the issue reporter:

Which is hooked up here:

vscode/src/vs/code/electron-sandbox/issue/issueReporterService.ts

Lines 1024 to 1027 in 6fb7d0a

	$('tr', undefined,
	$('td', undefined, 'GPU Status' as string),
	$('td', undefined, Object.keys(systemInfo.gpuStatus).map(key => `${key}: ${systemInfo.gpuStatus[key]}`).join('\n'))
	),