Update: add --fix to no-debugger (fixes #8659)

[aladdin-add]

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

[x] Add autofixing to a rule

What changes did you make? (Give an overview)
add --fix to no-debugger. (fixes #8659 )

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

[eslintbot]

LGTM

[mention-bot]

@aladdin-add, thanks for your PR! By analyzing the history of the files in this pull request, we identified @nzakas, @vitorbal and @btmills to be potential reviewers.

[aladdin-add]

should also update the docs?

[soda0289]

@aladdin-add Please update the docs. Checkout this commit for a sample of what should be added.
https://github.com/eslint/eslint/pull/7186/files

[eslintbot]

LGTM

[ilyavolodin]

Updating docs is no longer required. Build will automatically insert appropriate text in the right spot for rules that are fixable.

[btmills]

Sorry for the confusion around docs. Can you remove the change to the docs? Then this will be ready to go!

[eslintbot]

LGTM

[btmills]

LGTM, thanks @aladdin-add!

[aladdin-add]

@btmills done.

I thought the build will check it...

[kachkaev]

Not sure the change complies with

1. Avoid any fixes that could change the runtime behavior of code and cause it to stop working.

I wanted to use debugger; in dev and expected it to not automatically disappear on save due to prettier/eslint autofix. At the same time, I wanted debugger; to cause an error in npm run lint so that any case where this line is accidentally committed failed in CI. How to achieve such a behaviour after this PR?

Temporary have to write

// eslint-disable-next-line
debugger;

+300% to length in each case 😃

Not sure autofixing no-debugger is a good idea.

[platinumazure]

@kachkaev Long-term, what we are hoping is that editor integrations will be able to go through fixable errors and choose which autofixes to apply or not. Recent versions of ESLint should provide all the information the integration would need (i.e., which rule is reporting a particular violation, whether or not the error is fixable, etc.); it should be possible for the integration to filter out certain types of fixable errors and just report them without fixing them.

So in short, I would recommend filing an issue on the GitHub repo for your editor integration.