4.12.0: reek config_file_pattern no longer supported

[dueckes]

After upgrading to 4.12.0, reek no longer appears to be analyzing code when a custom configuration is specified, ala:

    metric.enabled = true
    metric.config_file_pattern = 'config/metrics/reek.yml'

Code is analyzed when the config_file_pattern is omitted.

[bf4]

Oops.. @MGotink @ggallen ?

[MGotink]

Looks like I've introduced this bug with #258, I'm looking into it.

[MGotink]

Hmm, we're passing the config file to the reek examiner here while it no longer needs a config file parameter: troessner/reek@7f4ed2b#diff-c22bbfa18994bc5b1a2f38e7304b7627R13

[andynu]

As @MGotink mentioned reek reworked its config api. Since a similar behavior can be achieved by placing a *.reek configuration in the current directory (or your home directory) I propose we remove the config_file_pattern configuration option.