Updates and enhancements for 1.0.0

[JeffTomlinson]

See this issue for the Aquifer 1.0.0 release milestone.

• Updates aquifer-coder to be compatible with Aquifer 1.0.0 branch.
• Makes configuration options more robust.
• Docs updated for compatibility with: https://github.com/aquifer/aquifer/pull/172

To test:

• [x] Load up this branch in your Aquifer project.
• [x] Create a test directory in modules/custom
• [x] Add a test.module and a test.js file to the module and populate both with code containing code standards errors for that language.
• [x] Run aquifer lint and ensure your errors are caught.
• [x] See the README for new config override format and options and test them to ensure they work as expected.
• [x] Run aquifer lint -t modules/custom/test/test.js
  • [x] Verify only the js file is linted
• [x] Run aquifer lint -t modules/custom/test/test.module
  • [x] Verify only the module file is linted

[chasingmaxwell]

@JeffTomlinson this was the output of running gulp lint in the aquifer-coder project itself.

[15:14:10] Using gulpfile ~/workspace/aquifer-coder/gulpfile.js
[15:14:10] Starting 'lint'...
[15:14:10] 
aquifer-coder.js
  109:10  error  Parsing error: Use of future reserved word in strict mode

✖ 1 problem (1 error, 0 warnings)

[15:14:10] Finished 'lint' after 248 ms

[chasingmaxwell]

@JeffTomlinson other than the linting error above, this seems good to go.

[JeffTomlinson]

Marking needs work as @patrickocoffeyo expressed interest in supporting globbing on the target path.