Update tests to run for JS targets

[OptimumCode]

Hi, this PR allows running tests for JS targets.

The old version of tests had the following problems:

• It is incorrect to compare NaN to another NaN using == operator. For Java Float.NaN == Float.NaN returns false (but Objects.equals(Float.NaN, Float.NaN) returns true , which is why tests work for Java). For JS it is a bit different.

  NaN compares unequal (via ==, !=, ===, and !==) to any other value — including to another NaN value.

  For NaN comparison, equals call was replaced with isNaN() method call.

• The hex and octal numbers are valid floating point numbers for JS (because under the hood Kotlin delegates conversion to JS dynamic cast). This is the toDouble implementation for JS platform

  public actual fun String.toDouble(): Double = (+(this.asDynamic())).unsafeCast<Double>().also {
      if (it.isNaN() && !this.isNaN() || it == 0.0 && this.isBlank())
          numberFormatError(this)
  }

  Tests for those values are ignored for JS platform.

@sschuberth please, take a look at the PR when you have time. Thank you!

[sschuberth]

@sschuberth please, take a look at the PR when you have time.

Done, though I'm not sure why, as I have no approval rights on this repo 😉

[OptimumCode]

Thank you for your review @sschuberth!
I wanted to tag @charleskorn but he does not appear in the completion list for some reason, and I accidentally tagged you instead)) don't know why - probably because it is a bit late here already)

[sschuberth]

I accidentally tagged you instead

No worries, I hope my review was useful still 😸

[OptimumCode]

No worries, I hope my review was useful still 😸

It definitely was! Thanks again

[charleskorn]

Thanks @OptimumCode and @sschuberth!