Remove verbose GC logging to file for Java/wildfly-ee7

[zloster]

This logging doesn't follow the project recommendation about the logs and IMO is affecting the benchmark results of Wildfly. But this gave me an idea about a new test type: which framework can fill a SSD disk faster. Or which framework logs are the biggest for given test run :)

[mention-bot]

Thanks @zloster for contributing to The Framework Benchmarks! @msmith-techempower, @nbrady-techempower and @codylerum, code you've worked on has been modified. If you have the chance, please review. If you wish to unsubscribe from these notices, please open a Pull Request with the commit message [ci skip] and your github name added to the userBlacklist array in the .mention-bot file.

[codylerum]

👍

[zloster]

No better results: https://www.techempower.com/benchmarks/previews/round14/r14p3-vs-r14p4.html#wildfly-ee7.json Just the normal variation for the test results.
So the detailed garbage collection logging is basically free for this setup and conditions.

[codylerum]

@zloster I'm guessing their are gains to be made by tweaking the thread settings. I believe the environment is 40 cores now and I don't know how many wildfly is configured to use by default.

[NateBrady23]

@codylerum the server environment is 80 cores, and you can access that via the CPU_COUNT env variable if you need to.