Add test KDoc Link to a class with quoted name should be resolved

[vmishenev]

Note: a quoted name is rendered as inlined code.

[whyoleg]

Here is how the following links are rendered on master (and Dokka 2.1.0-Beta):

/**
 * [`Quoted Class Name`]
 * [`test%^!@#_me`]
 * [String.length]
 * [`String.length`]
 * [String]
 * [String.`length`]
 * [`String.`length``]
 * [`hexToByteArray`]
 */

Should we create an additional issue to decide how such cases should be rendered? #3719 could be related.

(cc @berezinant just in case you might have discussed such cases during code-blocks rework)

[whyoleg]

@vmishenev K2 tests are failing with metaspace error. Could you investigate?
I see that it fails in our new DokkaBootstrap implementation.

[vmishenev]

K2 tests are failing with metaspace error. Could you investigate?

#4244

Should we create an additional issue to decide how such cases should be rendered?

As for me, it looks logical. Or do you have a proposal?

[whyoleg]

As for me, it looks logical. Or do you have a proposal?

I don't have a direct proposal, but it feels weird that we mix Kotlin syntax to reference quoted declarations with Markdown syntax for inline code blocks. I understand why this happens: [xxx] is a shorthand for [xxx][xxx], and so one is resolved based on Kotlin syntax, and the other based on Markdown syntax, where we have different meanings for backticks.

Here, I would expect all of the examples to render consistently:

• All declarations rendered as inline code or not at all.
• In case the declaration name requires backticks (has spaces), those backticks should be rendered.

JIC, here is what it looks like in the latest IDEA with support for backticks in KDoc:

And I do really like how it's done there; it's consistent.

I'm still not quite understanding why this is resolved:

`String.length`

But that's a question for the KDoc parser (probably also needs an issue)