Implements the LogOutputWindow vscode API for PowerShell extension and PSES logs received via LSP.

Recording.2024-10-18.170017.mp4

There will now be 3 separate log output panels:
PowerShell Messages logged for the PowerShell client and messages sent via the LSP adapter (prepended with [PSES])
PowerShell: Trace LSP Traces the LSP messages back and forth. Omnisharp messages will show up as traces here
PowerShell: Trace DAP Traces the DAP messages back and forth (already implemented)

This has several benefits:

1. Output to file is handled by vscode, we don't need our own custom handler anymore
2. Log levels and switching log levels handled by vscode, our code related to this (settings etc.) can be removed
3. Logs can be tailed and opened in separate editors within vscode, providing a very nice experience. Logs are visible using the log syntax highlighting which can be enhanced by my Crisp Logs Highlighter
4. Centralizes to vscode extension log folder that will be used with Issue Reporter, there's a contribution API for issue reporter where we can gather additional data as well (PR forthcoming)

Log windows do not appear unless enabled.

Right now the Log Verbosity with "Set Log Level" only controls the client-side logging level, but I hope in a future PR to be able to update the logging level of PSES dynamically. Has a minor LSP performance benefit but difficult to implement due to MEL not having dynamic log level change support natively, but I think I found a way with IOptionsMonitor to do it.

Should be merged with PowerShell/PowerShellEditorServices#2200

Fixes #5079

@andyleejordan I think you'll like this new utility function too for taking action on a config change:

	/**
	* Invokes the specified action when a PowerShell setting changes
	* @param setting a string representation of the setting you wish to evaluate
	* @param action the action to take when the setting changes
	* @param scope the scope in which the vscode setting should be evaluated. Defaults to
	* @param workspace
	* @param onDidChangeConfiguration
	* @example onPowerShellSettingChange("settingName", (newValue) => console.log(newValue));
	* @returns a Disposable object that can be used to stop listening for changes
	*/
	// Because we actually do use the constraint in the callback
	// eslint-disable-next-line @typescript-eslint/no-unnecessary-type-parameters
	export function onPowerShellSettingChange<T>(
	setting: string,
	listener: (newValue: T | undefined) => void,
	section: "powershell",
	scope?: vscode.ConfigurationScope,
	): vscode.Disposable {
	return vscode.workspace.onDidChangeConfiguration(e => {
	if (!e.affectsConfiguration(section, scope)) { return; }
	const value = vscode.workspace.getConfiguration(section, scope).get<T>(setting);
	listener(value);
	});
	}

EDIT: I see a flaw here, will fix :)

Currently pending microsoft/vscode-languageserver-node#1116 otherwise all of our log messages surface as "trace" with a header which is not ideal.

This is going to be so nice though.

No longer pending that, I wrote a new trace handler :).

Currently debating if I want to add realtime logging changes based on changing the LSP setting to this PR or save that for another one.

Love it, yay.

[andyleejordan]

Ok nice that there's more information now.