[Wasm] Small and very confusing typo in the plugin warning

[orchestr7]

What's done:

• Invalid suggestion in warning confuses Kotlin newbies

[orchestr7]

@ALikhachev as a last contributor in the history :) hey, small friendly ping. Looks like this PR is not so heavy to take :)

[orchestr7]

@demiurg906 @Tapchicoma @dimonchik0036 @cypressious tagging you as top contributors for the last month. May be you can give insights on how to merge small PRs like this one into Kotlin? :)

Hate having open PRs in my dashboards

[JSMonk]

@orchestr7 Sorry for waiting so long. And thank you for the contribution 🙏
I've asked @ilgonmic to take a look and approve these small changes.

[ilgonmic]

Hi, thank you!
Good catch
LGTM
I could process the review later

[dimonchik0036]

Shouldn't it be covered with tests? A good practice is to have a commit with test data to reproduce the issue, and then a fix for it (if this is applicable for a test).
An example: test + fix

[orchestr7]

Shouldn't it be covered with tests? A good practice is to have a commit with test data to reproduce the issue, and then a fix for it (if this is applicable for a test).

Haha 😄
Then, if it's a good practice, there should be a regression test for this logging?

PS but sure, Dima, I will add it, if needed, np