[eslint] enforce import plugin rules

[rosskevin]

Most of the eslint-import-plugin rules were disabled. I added the webpack resolver, pointing it at the docs/webpack.dev.config.js as it had the aliases setup that check most of the code.

I removed disabled rules and configured a few local exceptions using subordinate eslintrc.js files.

Since we make one eslint run, we have to disable import resolution checks in some cases because we are using multiple package.json files, and it is one execution to one package.json. I focused on hardening the src imports and secondarily docs.

Aside from setup, I fixed a few import related consistency issues that it exposed.

• PR has tests / docs demo, and is linted.
• Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
• Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

[rosskevin]

I'm working on the error, it only fails on circleci and I can't quite track it down so I'm ssh'd into the build trying to track it down. If anyone knows how the ci build error is related, please let me know.

[rosskevin]

Found it.