Remove extraneous string escape from convert to template string refactor

[andrewbranch]

Fixes #37330

String literal text should be transferred to template head/tail text without modification—it gets escaped in the printer.

[sandersn]

one tiny style comment

[andrewbranch]

@orta, playwright failed to install all of a sudden on node 8 both in Actions and in Pipelines. Have you seen this before? 🤔

[orta]

No, this sounds like the first time it's failed full stop

[orta]

Because the dep isn't locked, it looks like it needs bumping to node 10

[thw0rted]

I can't tell if this is supposed to have landed in production yet. I'm running VSCode 1.49.0, which I think is TS 4.0 under the hood. Should I expect the behavior I'm seeing to include this PR?

I came here because I just converted "\b" + query + "\b" to a template and got "missing character" unicode boxes, i.e. `�${query}�`, as the result.

The missing character I pasted in there looks like an empty square in the GH Markdown editor but a question-mark inside a black diamond in the preview. I copied the character, then pasted into the Chrome dev tools console as "{paste}".charCodeAt(0), which returns 8 -- so it's converting the nice readable backspace escape sequence into a literal backspace character.

Obviously, in my case I actually meant to write "\\b" + query + "\\b" -- it was an oversight in the original code. But the TS convert-to-template refactoring feature is changing the escape sequence to a literal. I checked and this happens for all escape sequences: newline, form-feed, etc. I'm pretty sure it shouldn't, and I'm trying to figure out if it was fixed by this PR, or if the PR introduced the bug.

I guess what I'm asking is, should I open a new issue?

[andrewbranch]

@thw0rted yes, if you could open a new issue, that would be great. Thank you!