[Suggestion] Add module configuration extendability

[bekh6ex]

A possible way to add configuration to individual modules

To try out documentation

./bin/hawkeye modules config files-secrets

[bekh6ex]

removeAdditional - remove additional (nondocumented) properties from config object. Might be useful to force module developers documenting all possible config values.
useDefaults - if property is not defined and has default value will modify config object by injecting the property with default value. Just handy.

[bekh6ex]

To generate reasonable documentation (help) we can enforce by tests things like:

• each config should have an example (that is up to date and passes schema test)
• each property has a title and a type
• ...

[bekh6ex]

Also we can try to use this definition for cli arguments. Not sure how hard it will be if we want to make it good

[bekh6ex]

... or limit cli arguments to what we have now and allow to pass .hawkeyerc as an argument or even read it from stdIn

[bekh6ex]

Currently, when executing ./bin/hawkeye modules config files-secrets I get this output:

[info] Version: v1.6.1
files-secrets module configuration properties:

    files (string[]): List of files containing patterns of suspicious filenames

.hawkeyerc examples:
{
  "moduleConfig": {
    "files-secrets": {
      "files": [
        "path/to/patterns.json"
      ]
    }
  }
}

[bekh6ex]

@felixhammerl Any comments on this?