Support fully qualified type names

Logging frameworks such as [oshai/kotlin\-logging](https://github.com/oshai/kotlin-logging) use invocations like this to automatically assign a logger name:
```kotlin
private val logger = KotlinLogging.logger {}
```

Behind the scenes, they use `KClass.qualifiedName` which does not produce a fully qualified name on Js.

This plugin could solve that, e.g.:

* A file-level logger in `MyFile.kt`

```kotlin
package com.example

val logger = Logger(__QUALIFIED_CLASS__) // "com.example.MyFileKt"
```

* A class-level logger

```kotlin
package com.example

class MyClass {
companion object {
val logger = Logger(__QUALIFIED_CLASS__) // "com.example.MyClass"
}
}
```

In an internal project, I had created an annotation-based compiler plugin to generate logger names (also via a `IrElementTransformerVoidWithContext` derivative). The relevant qualified class name (including Kotlin's invisible file-level classes) was retrieved like so:

```kotlin
val qualifiedSurroundingClassName = allScopes.reversed().firstNotNullOfOrNull {
it.scope.scopeOwnerSymbol.owner.qualifiedClassName()
}
if (qualifiedSurroundingClassName == null) {
reportError("Could not find a qualified class name", call)
return super.visitCall(call)
}
```

Start by tracing the compiler plugin's IR transformation around logger calls, using the IrElementTransformerVoidWithContext and qualifiedClassName approach shown in the issue. Check the file-level and class-level examples, including Kotlin's invisible file-level classes. Done means logger names include the expected fully qualified names on Js.

Written by the indexing model from the issue text.