Update: Drop @typescript-eslint/eslint-recommended from eslint --init

[NMinhNguyen]

@typescript-eslint/recommended now extends from @typescript-eslint/eslint-recommended:
https://github.com/typescript-eslint/typescript-eslint/releases/tag/v3.0.0

/cc @bradzacher

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[X] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

Removed @typescript-eslint/eslint-recommended because it's no longer necessary.

Is there anything you'd like reviewers to focus on?

No

[kaicataldo]

I don't think we should do this yet because this would not enable the rules for anyone still on the previous major release line (most likely the majority of users, since this was just released). If we want to do this, we need to add a check to see if @typescript-eslint/eslint-plugin is v2 or v3 and adjust the config accordingly.

[NMinhNguyen]

Oh I was under the impression that eslint --init was for bootstrapping from scratch (e.g. the file is called config-initializer implying there’s no existing config and one is being initialised) and that by default it would install the latest version (v3) of @typescript-eslint dependencies

[nzakas]

@kaicataldo I believe this is safe to change. We are installing the latest typescript-eslint when doing --init, so the latest recommendation for how to setup a config should be followed.

[kaicataldo]

Thanks for contributing!