Support npm transitive dependencies with esbuild

In the meantime this hack would do:

```kotlin
open class EsbuildCreateSymLink : DefaultTask() {
private val realNodeModules = File(project.buildDir, "js/node_modules")
private val linkNodeModulesProd = File(project.buildDir, "compileSync/js/main/productionExecutable/kotlin/node_modules")
private val linkNodeModulesDev = File(project.buildDir, "compileSync/js/main/developmentExecutable/kotlin/node_modules")

@TaskAction
fun run() {
for (linkNodeModules in listOf(linkNodeModulesProd, linkNodeModulesDev)) {
linkNodeModules.parentFile.mkdirs()
if (!Files.isSymbolicLink(linkNodeModules.toPath())) {
Files.createSymbolicLink(linkNodeModules.toPath(), realNodeModules.toPath())
}
}
}
}

tasks {
val esbuildCreateSymLink by creating(EsbuildCreateSymLink::class) {
dependsOn("kotlinNpmInstall")
}

val browserDebugEsbuild by getting {
dependsOn(esbuildCreateSymLink)
}
}
```

Start by tracing how the Kotlin/Gradle build invokes esbuild and installs npm dependencies, using the EsbuildCreateSymLink task in the issue as the current workaround. Done means transitive npm dependencies are available to esbuild for production and development builds without requiring the symlink hack.

Written by the indexing model from the issue text.