<inheritdoc> doesn't work with fully qualified crefs

[joshua-light]

Currently, crefs are resolved only when they're specified using short names.

E.g.

/// <inheritdoc cref="A(List{int},byte)" />
public static void A(List<int> x, int y) => ...;

public static void A(List<int> x, byte y) => ...;

We should also resolve crefs like this:

/// <inheritdoc cref="A(System.Collections.Generic.List{int},byte)" />
public static void A(List<int> x, int y) => ...;

public static void A(List<int> x, byte y) => ...;

[joshua-light]

This feature is somewhat tricky since we don't work with symbols as this increases the generation time dramatically.

However, what we could do at least:

• Try to search types that end with the cref value (ignoring parameters and type-parameters)
• If any matches, then consider that it's very likely this is also a referenced type
• Prefer types that are from the existing project vs standard ones.

This should work in 80% of the cases since we have access to the project being generated (we have all syntax trees from it) as well as System assembly which is always loaded (there could be minor mismatches, though, suppose our generator is .NET 8.0 but it generates documentation for .NET Framework 4.8 project).

We could also consider having additional optional parameters that specify paths to assembly that we could load dynamically and use as a pool of names.