Docs: clarify that space-unary-ops doesn't apply when space is required

[tmdesigned]

Prerequisites checklist

• I have read the contributing guidelines.

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

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

What changes did you make? (Give an overview)

Updated docs for space-unary-ops to clarify that the words operators are only considered when a space is not required for proper syntax.

This was previous confusing, as the "incorrect" examples were ones that had optional spaces (i.e. delete(foo)) while the "correct" examples were ones that required spaces anyways (i.e. new Foo). Therefore, in addition to a note under the rule description, the examples were modified to more closely mirror each other to make the actual rule clearer.

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

[eslint-deprecated]

Hi @tmdesigned!, thanks for the Pull Request

The pull request title 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 length of the commit message must be less than or equal to 72

Read more about contributing to ESLint here

[kaicataldo]

Closed and reopened to fix the CLA check.

[mdjermanovic]

Thanks for the PR!

while the "correct" examples were ones that required spaces anyways (i.e. new Foo)

Completely agree, the correct examples for words were not very useful.

[mdjermanovic]

This clarifies a lot, thanks! I just have a note about the added incorrect example.

[mdjermanovic]

LGTM, thanks!

[kaicataldo]

Thank you!