fix: Fix more Escape conflicts

[calculuschild]

Marked version: 5.0.4

Markdown flavor: GFM

Description

• Simplifies the previous solution from fix: Support escapes within emphasis #2627, and also fixes some missing edge cases mentioned therein: comment

What was attempted

Literally the only cause of #2280 failing was because \ was not included in the punctuation list. I added that, and undid the complex solution from #2627.

Also changed the "mask out escaped EmStrong" code to mask out all escaped tokens, which handled the new test case _\\_ where the backslash is itself escaped. Could have been handled by a more complex escapedEmStrong regex, but this solution I think can apply to a few other locations where escapes come up, in a future cleanup PR, and doesn't appear to add any slowdown compared to the current solution.

Contributor

• Test(s) exist to ensure functionality and minimize regression (if no tests added, list tests covering this PR); or,
• no tests required for this PR.
• If submitting new feature, it has been documented in the appropriate places.

Committer

In most cases, this should be a different person than the contributor.

• CI is green (no forced merge required).
• Squash and Merge PR following conventional commit guidelines.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
marked-website	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 5, 2023 5:17pm

[UziTech]

According to recheck those regexps are safe. 👍

[styfle]

Thanks!