LogConfigurator resolveConfig  also reads .rpmnew or .bak files

Currently the LogConfigurator will attempt to read any file that starts with "logging." in the env.configFile() path.

A common practise is to suffix files with .bak or in case of package managers they often add a suffix if the file has been modified upstream.

Elasticsearch will read those values anyway and that might lead to very confusing logging behaviour.

I am not sure how to best approach this, either have a whitelist or a backlist of suffixes that are allowed/disallowed ?
Not sure you got my previous comment on this, it might have gotten lost with the rebase. I think we can avoid using the  `TemporaryFolder` rule but just rely on the facilities provided by the randomized testing library. We can just create a new directory within the globalTempDir() that is already available (via the `newTempDir()` static method), and then create the file within this temp dir that gets cleaned after each test by default. Also, this should make it possible to merge this new class with the existing `LogginConfigurationTests`. Makes sense?