Make use of both detail and documentation fields

[meganrogge]

When we have a command that has both a description and a path, we should show those both similar to what the editor does.

We'd need to add documentation to our API.

vscode/src/vscode-dts/vscode.d.ts

Lines 4919 to 4927 in ff59377

	* A human-readable string with additional information
	* about this item, like type or symbol information.
	*/
	detail?: string;
	/**
	* A human-readable string that represents a doc-comment.
	*/
	documentation?: string | MarkdownString;

[meganrogge]

cc @Tyriar

[meganrogge]

We do not show simultaneously because they provide the same info, so it would be redundant to do so.

Verify that when you open the suggest widget in the terminal and type code-insiders, for example, you see the command path description. Use ctrl+space to open documentation, which will show the command's description and path.

[alexr00]

I set "terminal.integrated.suggest.enabled": true, but I don't get terminal suggestions. Anything else I need to do?

[meganrogge]

@alexr00 waiting for this build to finish which fixes terminal suggest https://monacotools.visualstudio.com/Monaco/_build/results?buildId=316161&view=results

[roblourens]

I got the new build, and I only see files in zsh, no commands

[meganrogge]