Github Actions improvements, Revert karma config, and add KotestProjectConfig

[nomisRev]

In #2874 we increased property test iterations from 250 to 1000 here.

We then later had to add karma.config to fix timeouts on JS platform, since running 1000 iterations was taking so long that the browsers considered the tests timing out.

This PR reverts the karma.config, and uses KotestProjectConfig to set iterations back to 250. This was done because I noticed some flakiness issues on JVM using 1000 iterations on Github Actions 😞

[nomisRev]

check is still flaky with this change 😞

@serras Whenever I check the failed check task I see an enormous amount of log output related to classpath of Optics KSP tests. Do you know if this is something we can disable, or configure? Or is this out of our control? All the output seems unnecessary to always be logged, it seems like INFO or DEBUG level logging.

[serras]

It's printed by us in this line. I'm happy if you just comment it out, it adds no value outside of debugging environments.

[github-actions]

Kover Report

Total Project Coverage	42.20%

[JavierSegoviaCordoba]

I would only change the jvmTest part