Fix LSP reporting wrong types

[Razoric480]

Classes were properties, functions interfaces, variables weren't distinguished from properties, functions from methods, etc.

Fixes #50815 and fixes #50822 . 4.0 companion to #50914 .

[akien-mga]

Thanks!

[atirut-w]

Thank you so much :D

[raulsntos]

Why was the SymbolKind enum changed? It seems vscode defines it as 0-based, see https://github.com/microsoft/vscode/blob/459ffea03c117042c17c6a3c02f066c4af5db555/src/vs/editor/common/languages.ts#L1175-L1202.

[Razoric480]

The LSP spec defines it as 1 based, and as I recall when I made this PR, there was a 1 off error.
https://microsoft.github.io/language-server-protocol/specification#textDocument_documentSymbol

[raulsntos]

I see, but since the Godot vscode extension uses the enum defined by vscode which is 0 based, wouldn't that cause issues?

[Razoric480]

In the VSCode LSP client protocol, there are functions like:

function asSymbolKind(item: ls.SymbolKind): code.SymbolKind {
		if (item <= ls.SymbolKind.TypeParameter) {
			// Symbol kind is one based in the protocol and zero based in code.
			return item - 1;
		}
		return code.SymbolKind.Property;
	}

to account for such discrepencies.