fix: Handle escape and regex characters

[saig0]

Description

Correct the handling of escape sequences in string literals.

Don't replace escape sequences in regex expressions, for example, \r or \n. In the parser, these sequences start with \. Same for \s, don't replace it with a whitespace, since this is also a part of a regex.

Handle \ to avoid that the sequence is escaped and returned as \\.

"\s\r\n"
// before: " \r\n"
// after:  "\\s\r\n"

"\\s\\n\\r"
// before: "\\ \\\n\\\r"
// after:  "\\s\\n\\r"

Related issues

closes #883
closes #879

[saig0]

@mboskamp I fixed the issue with \s character. I did an integration test in C8 and it looks good from my perspective. ✅

However, it is important to note that "\s" is not a valid string literal because \s is not an escape character. Instead, it should be "\\s". Same for \n and \r, if both characters are used for a regex then they should be escaped as \\n\\r. As a result, the string in the example DMN should be "\\s\\r\\n" instead of "\s\r\n".

[mboskamp]

👍 Looks good. I did not test this in C7 and did not fully understand the fix. However, the test cases look good.

[backport-action]

Backport failed for 1.16, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin 1.16
git worktree add -d .worktree/backport-930-to-1.16 origin/1.16
cd .worktree/backport-930-to-1.16
git switch --create backport-930-to-1.16
git cherry-pick -x c8b01bd09f2cf6fca2bc789a2101001c99778480 58efca98cca80dcdb7d9dc28c2331e9991b63956 544c0388bb0ee8e9a3b078f4567941ce684a8f0a d266e80173126eaf6dbfee4333be6cb0833c39bf

[backport-action]

Successfully created backport PR for 1.17:

• [Backport 1.17] fix: Handle escape and regex characters #932

[backport-action]

Successfully created backport PR for 1.18:

• [Backport 1.18] fix: Handle escape and regex characters #933