Feature: Ability to get official documentation URL of a symbol e.g. method or function

Consider these use cases:

1. I see GetFullPathNameW, and the signature helper is not giving me enough info, then I need to go to the Official docs.microsoft.com page to get more info.
2. I see symbol mysqli_multi_query, then I want to see how it was used, I need to go to https://php.net/mysqli_multi_query
3. I see a symbol components then I need to go to the page doc.rust-lang.org to see examples and more info about the type it actually returns.

Examples could go on, but the point remains the same. It's not enough to have a signature help alone these days, it would be beneficial if language server had a way to give an Symbol -> External URL action. Naturally for this to work each language server, and used library needs support also.

Thanks for considering.

For instance such an linking field could be in SignatureInformation, e.g.:

export interface SignatureInformation {
        documentationUrl?: string; // <- new optional field here

	label: string;
        documentation?: documentation?: string | MarkupContent;
        parameters?: ParameterInformation[];
        activeParameter?: uinteger;
}

The issue points to the TypeScript SignatureInformation interface and proposes an optional documentationUrl field for external symbol documentation. Start by reviewing that interface and related protocol definitions, then determine how a language server should expose URLs across the cited examples. Done means the protocol shape and its intended behavior are clearly decided and documented.