Implement LogOutputWindow for Logging

[JustinGrote]

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

Recording.2024-10-18.170017.mp4

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)

A sister PR for PSES (everything coming across the LSP currently shows up as info) is forthcoming but is not urgently necessary to merge this PR.

[JustinGrote]

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

vscode-powershell/src/utils.ts

Lines 89 to 113 in d617194

	/**
	* 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 :)

[JustinGrote]

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

[andyleejordan]

This is going to be so nice though.

[JustinGrote]

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.