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 ?
with the current code a `logging.whatever.yaml` file would be loaded. I wonder if this is our intention or a side-effect of the current behaviour. Honestly I would be in favour of simplfying this further and even have something like `if (file.getFileName().toString().equals("logging.yaml") || file.getFileName().toString().equals("logging.yml") )` unless we want to extend this to json and properties files, which I think would be off-topic in this PR.