New: Add eslint-plugin-eslint-plugin to plugin generator

[bmish]

Partially fixes #65.

We want to encourage the adoption of eslint-plugin-eslint-plugin to help ESLint plugin authors follow best practices including avoiding using deprecated APIs and producing rules with good usability.

I'll follow-up after this to add eslint-plugin-node and make some other improvements too.

[eslint-github-bot]

Hi @bmish!, thanks for the Pull Request

The first commit message isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag must be one of the following:

  The Tag is one of the following:

  • Fix - for a bug fix.
  • Update - either for a backwards-compatible enhancement or for a rule change that adds reported problems.
  • New - implements a new feature.
  • Breaking - for a backwards-incompatible enhancement or feature.
  • Docs - changes to documentation only.
  • Build - changes to build process only.
  • Upgrade - for a dependency upgrade.
  • Chore - for anything that isn't user-facing (for example, refactoring, adding tests, etc.).

  You can use the labels of the issue you are working on to determine the best tag.

• There should be a space following the initial tag and colon, for example 'New: Message'.

• The first letter of the tag should be in uppercase

Read more about contributing to ESLint here

[nzakas]

Please check the file conflicts.

[bmish]

Fixed conflicts. I'll open up several more PRs after this.

[snitin315]

Looks good.