LSP does not prohibit empty symbol names, but VS Code rejects them

[tchebb]

DocumentSymbol and SymbolInformation each hold a name field, defined only as a string that is "The name of this symbol." However, VS Code applies an additional constraint that the symbol name not be empty. This ambiguity recently caused the Rust Language Server to fail to populate VS Code's outline view (see rust-lang/rls#1193). If empty symbol names are actually prohibited, can the LSP spec reflect that?

[dbaeumer]

This got addressed in the 3.15 spec thanks to your PR.