feat: directive prologue detection and autofix condition in quotes

[fasttime]

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
[x] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

see #17022

What changes did you make? (Give an overview)

This PR implements two changes in the quotes rule:

• Fixed detection of directive prologues to account for parentheses around string literals, e.g. differentiate "use strict"; from ("use strict");. This can cause the rule to report new problems in certain cases.
• Changed the logic that determines whether an autofix can be applied or not, in line with no-extra-parens: unparenthesized string literals that are direct children of an ExpressionStatement will not be autofixed.

Both changes were discussed in #17022, but we decided to postpone them to a new PR.

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

Shall we add a note to the documentation, like in no-extra-parens?

[mdjermanovic]

Shall we add a note to the documentation, like in no-extra-parens?

I personally think there's no need to document edge cases where rules don't autofix the code, but we could add some "correct" examples for this rule with the "backtick" option where string literals must be string literals (e.g., directives and property names in object literals).

[nzakas]

I think it's helpful to add a note to the documentation because there isn't any mention of directives right now. Something along the lines of, "This rule is aware of directive prologues such as "use strict" and will not flag or autofix them unless doing so will not change how the directive prologue is interpreted."

[fasttime]

Thanks for your feedback @mdjermanovic @nzakas. I've updated the documentation as suggested (in 6f7b899).

[nzakas]

A little difficult to parse, maybe:

Suggested change

	This rule is aware of directive prologues such as `"use strict";` and will not flag or autofix them unless doing so will not change how the directive prologue is interpreted.
	This rule is aware of directive prologues such as `"use strict"` and will not flag or autofix them if doing so will change how the directive prologue is interpreted.

[fasttime]

Thanks! I thought that the semicolon in "use strict"; would make it clearer that what is shown is a directive as opposed to just a string, but it that's bad for readability we can leave it out.

[nzakas]

Yeah, dangling semicolons are a little visually confusing. :)

[nzakas]

LGTM. Would like @mdjermanovic to review before merging.

[mdjermanovic]

LGTM, thanks!