Support array of config_files in Hound configuration

[robbymarston]

I'm working on a project that uses several different JavaScript frameworks (Vue and React) in different areas of the application. As such, it requires multiple configurations for linters such as sass-lint. This works fine locally as my IDE automatically parses the multiple sass-lint configuration files at the root and in any subdirectories. This seems to be standard practice for plugins with standalone configuration files. Ideally, Hound work 'pick up on' any configuration files with standard naming; but given that that may be difficult to maintain, it should at least support multiple config_paths ala:

sass-lint:
   config_file:
      - sass-lint.yml
      - path/to/another/sass-lint.yml     

[gylaz]

@robbymarston Thanks for opening an issue with a potential solution. This is similar to #889. I agree, something needs to be done in this case.

Couple of questions here:

• Does path/to/another/sass-lint.yml apply to any file that's in path/to/another directory or its children?
• Does path/to/another/sass-lint.yml need to be merged/combined with sass-lint.yml (or any other config file in between the two dirs) when linting files under path/to/another/*?

[gylaz]

Here are some additional thoughts from another related issue: #1210 (comment)