Allow the various linters to be configured via their standard config files

[jobara]

Is your feature request related to a problem?

It might be easier for a user of fluid-grunt-lint-all to be able to use the standard config files, e.g. eslintrc.json and etc. to configure the settings of the various fluid-grunt-lint-all plugins. IDEs can already be setup to use these configuration files to provide linting during coding/writing. Also, it may be clearer for those coming into the project to understand what and where to find the configuration.

Describe the solution you'd like

Use standard configuration files for the various linters, instead of configuring through grunt, although that could still be an option for overrides if necessary.

Additional context or notes

Config file changes coming to eslint: eslint/rfcs#9

[the-t-in-rtf]

As we've discussed elsewhere, some ESLint settings overlap with settings specific to Grunt (notably, which files to include/exclude). We need a strategy for dealing with this overlap. There is also the option to specify that an entirely different configuration file should be used. If we're going to keep using grunt-eslint, whatever we come up with has to ensure that we don't special case the configuration file names we prefer in a way that limits people's options to use different names or conventions.

Longer term, we also need to discuss this in combination with moving away from Grunt, which I've filed as #21

The simplest change for now might be to simply use the configFile option more widely. We should at least review the plugins we use and see whether they have a configFile option, and if so, whether we can make them better aware of our settings files by adding settings.

[the-t-in-rtf]

As mentioned in #21, we also support our own syntax for includes and excludes, so if we start respecting central configuration files, we'd either need to update that support, or perhaps follow a strategy like React's scripts, where they disallow the use of particular configuration options.