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 ?
Actually, I think we can do this without a `TemporaryFolder`. We can just write a new file within the `globalTempDir()` that is already available, no need to create a new folder. Also, this should make it possible to merge this new class with the existing `LogginConfigurationTests`.