Make it more obvious knit doesn't care how your modules are managed

[shanewilson]

By default we are pushing that users should put their modules in modules/node_modules because we think that is the best way to handle this problem, but since knit doesn't actually execute the code we can leave that decision entirely up to the application developer.

as long as the folder structure is something like:

<PATH_TO_MODULES_DIR>
  - moduleA/
    - package.json
  - moduleB/
    - package.json

setting knit.needle.paths.modulesStub: PATH_TO_MODULES_DIR in root package.json should be enough to get knit to see the modules and run dependency checks across them.