Support for cref in inheritdoc tags

[matkoch]

Following up on #247.

In regards to this comment, I would like to refer to my comment in the related roslyn issue again.

[Still34]

Would this ever be supported? I'd like to see it in v3 if possible.

[rymeskar]

+1, to be more precise.

In fact, I would appreciate an introduction of all the currently non-supported features from the list.

[amirebrahimi]

Any feedback before I create a PR? Here's my proposed solution:
1ae5ba1

[rymeskar]

For completeness, please make sure the documentation is updated.

[superyyrrzz]

@rymeskar Sure. It will be updated along with docfx release.

[kygagner]

As far as I can see from the commits for this PR (https://github.com/dotnet/docfx/pull/5491/commits), none of the commits actually made it onto main. Actually, Github says these commits aren't on any branch. So, is this really fixed, or do we need to merge this change in again?

[yufeih]

<inheritdoc> implementation was updated to behave the same as Roslyn in #8589, both <cref> and <path> should be supported in after v2.65.0.

[kygagner]

@yufeih I am using version 2.67.1 and the entire inheritdoc feature is not working for me, but I will do some more investigation on my end. Thanks for pointing me to the latest PR.