non_ascii_literal, invisible_characters: don't suggest a fix on raw strings

[shulaoda]

Both non_ascii_literal and invisible_characters build their suggestion from the source snippet and inject \u{...} escapes into it. Those escapes are inert inside a raw string literal, so cargo clippy --fix corrupts raw strings: the real character is dropped.

For a raw string literal the lints now keep the warning but only emit a help to use a normal string literal, instead of a machine-applicable suggestion that would corrupt the code. Cooked strings, char literals and unicode_not_nfc are left unchanged.

Fixes #9805

changelog: [non_ascii_literal]: warn without a suggestion on raw strings instead of suggesting a fix that corrupts them
changelog: [invisible_characters]: warn without a suggestion on raw strings instead of suggesting a fix that corrupts them

[rustbot]

r? @dswij

rustbot has assigned @dswij.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

• Owners of files modified in this PR: 8 candidates
• 8 candidates expanded to 8 candidates
• Random selection from Jarcho, dswij, llogiq, samueltardieu

[github-actions]

Lintcheck changes for 04ac508

Lint	Added	Removed	Changed
clippy::non_ascii_literal	0	0	2

This comment will be updated if you push new changes