Create LocalizationHoverProvider

[Shresht7]

Register a hover provider for localization handles in localization (XML) files that show the content associated with the handle.

Fixes #28

[Shresht7]

Right now, the localization references are built once (when the extension activates). To keep the references up to date, a file-system watcher can be used to update, rebuild and remove localization handler references as needed.

here's a quick draft sketch of what it would look like:

const localizationXMLFileWatcher = vscode.workspace.createFileSystemWatcher("**/Localization/**/*.xml");

localizationXMLFileWatcher.onDidCreate(e => {
	vscode.window.showInformationMessage(`CREATE: ${e.fsPath.split("\\").at(-1)}`);
	buildLocalizationReference();
});

localizationXMLFileWatcher.onDidChange(e => {
	vscode.window.showInformationMessage(`CHANGE: ${e.fsPath.split("\\").at(-1)}`);
	buildLocalizationReference();
});

localizationXMLFileWatcher.onDidDelete(e => {
	vscode.window.showInformationMessage(`DELETE: ${e.fsPath.split("\\").at(-1)}`);
	removeLocalizationReference();
});

[Shresht7]

It's starting to take shape.

Considering each localization xml contributes its own handles and content, it may be prudent to register separate hover providers for each file (and dispose them off if they're deleted). This will isolate the reference map objects.

That said, how often do I expect the localization files to be removed? for this to even be a issue. Even then a simple reload the editor will "fix" the problem.

[Shresht7]

Because of 9dca9ac, bumpVersionNumber command now fails as it cannot find the lsx version regex. I can point it to the VersionHoverProvider but this will need a proper solution eventually.