Adjust the JVM options to heal the Native build on CI

[danicheg]

It's been five years since these options were last touched. Too many things have become complicated since then. But let's see if this actually fixes the Native build.

[danicheg]

Mentioning the original issue with the Native build:

[error] Test runner interrupted by fatal signal 11
[warn] Force close java.lang.RuntimeException: Process /home/runner/work/cats/cats/tests/native/target/scala-2.13/cats-tests-test finished with non-zero value 139 (0x8b)

[danicheg]

One might speculate that solving infrastructural issues by simply increasing resources isn't wise. It's a fair point. On the other hand, we've had three consecutive 'green' CI runs with these tweaks (#1, #2, #3).

[armanbilge]

Nice. GitHub recently upgraded their runners so we have 16GB memory (I think the old limit was 7GB). We can't give it all to the JVM because Native (and JS) run their test suites as a separate process.

https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories