[Wasm] Don't try to lazy-initialize properties with 'definedExternally'

NFC for K/JS since externals live in a separate place

compiler/ir/backend.js/src/org/jetbrains/kotlin/ir/backend/js/lower/PropertyLazyInitLowering.kt

@@ -284,7 +284,7 @@ private fun <T> IrDeclaration.withPersistentSafe(transform: IrDeclaration.() ->
 
 private fun IrDeclaration.isCompatibleDeclaration(context: JsCommonBackendContext) =
     correspondingProperty?.let {
-        it.isForLazyInit() && !it.hasAnnotation(context.propertyLazyInitialization.eagerInitialization)
+        !it.isExternal && it.isForLazyInit() && !it.hasAnnotation(context.propertyLazyInitialization.eagerInitialization)
     } ?: true && withPersistentSafe { origin in compatibleOrigins } == true
 
 private val compatibleOrigins = listOf(

js/js.translator/testData/box/native/kt2209.kt

@@ -1,6 +1,4 @@
 // EXPECTED_REACHABLE_NODES: 1281
-// IGNORE_BACKEND: WASM
-// WASM_MUTE_REASON: LAZY_INIT_PROPERTIES
 package foo
 
 external interface Chrome {