Reduce flakyness of Resource tests

[jaydeluca]

This test is 43% flaky

Looking at the failures, it is that the host.arch attribute is not reliable

Moving the Security Manager tests to their own test suite to avoid them altering the environment, causing issues with other tests

[laurit]

I think this is not a good way to fix this issue. The reason this test is flaky (it actually reliably fails on the first execution and passes on retry) is that it depends on the order tests are run. If

opentelemetry-java-instrumentation/instrumentation/resources/library/src/test/java/io/opentelemetry/instrumentation/resources/HostResourceTest.java

Line 40 in 2d5775a

static class SecurityManagerEnabled {

is run first it will poison the environment for this test. Even if you ignore host.arch you'll next run into the same issue with os.description (at least that is what happened when I disabled HostResourceTest.SecurityManagerEnabled). Perhaps we should move all the security manager tests to a separate suite so they couldn't interfere with the main suite.
I can reliably reproduce this with running ./gradlew :instrumentation:resources:library:clean and ./gradlew :instrumentation:resources:library:test --no-build-cache -PtestJavaVersion=8