Move rule configuration to a JSON file about repolinter

[iamwillbar]

I'm thinking we should adopt something similar to the ESLint format, based on our current rules it would look something like this:

{
  "rules": {
    "license-file-exists": ["error", {"files": ["LICENSE*", "COPYING*"]}],
    "readme-file-exists": ["error", {"files": ["README*"]}],
    "contributing-file-exists": ["error", {"files": ["CONTRIB*"]}],
    "readme-references-license": ["error", {"patterns": ["license"]}],
    "readme-references-code-of-conduct": ["error", {"patterns": ["code of conduct"]}],
    "binaries-not-present": ["error", {"extensions": ["*.exe", "*.dll"]}],
    "license-detactable-by-licensee": ["error"],
    "test-directory-exists": ["error", {"directories": ["test*", "specs"]}],
    "source-license-headers-exist": ["error", {"files": ["**/*.js"], "ignores": "node_modules/**", "lineCount": 5}]
  }
}

Thoughts?

[trevmex]

I think that is a good first go. Let's do it.

[trevmex]

let's put it in a config/ directory (eg. config/repolint.json)

[bkeepers]

I think that's a good start.

[iamwillbar]

@trevmex most existing tools (grunt, eslint, jslint, tslint, etc.) don't use a subdirectory, I'll configure it to look both in the target directory as well as target directory/config so people have a choice.

[trevmex]

PR #17 addresses this.