fix: correct broken backslash display and enhance escape characters section

[CybotTM]

Summary

• Fix the broken backslash rendering from Fix escape character notation in RstCheatSheet #507
• Replace the :rst: text role with inline literal (double backticks) which renders correctly
• Add more escape examples (backticks, underscores, backslash itself)
• Add note clarifying that escaping is not needed inside code blocks

Context

PR #507 attempted to fix the backslash display by using the :rst: text role, but as confirmed by @franzholz and @ineswillenbrock, the backslash is still not rendered.

Root cause: A backslash immediately before the closing backtick is consumed by the RST parser as an escape sequence — the text role handler never receives it. See upstream issue: TYPO3-Documentation/render-guides#1188

Fix: Use inline literal markup instead, which handles the backslash correctly:

- you must escape it with a prepended :rst:`\`.
+ you must escape it with a prepended backslash (``\``).

Test plan

• Verify the backslash renders correctly in inline code on the rendered page
• Verify the additional code block examples render correctly
• Verify the ref link in the note resolves correctly

[franzholz]

I would say a hint to " :rst:`\`" should be given as alternative option in the note box with the comment, that this way should work in the future.

[franzholz]

I have tested my original commit. And it also works. Shouldn't it be mentioned as a second alternative? Then everyone can choose his preferred way.

b71a7fb

with its normal meaning, you must escape it with a prepended "\\".

[CybotTM]

I would say a hint to " :rst:\" should be given as alternative option in the note box with the comment, that this way should work in the future.

IF

:rst:`\`

finally works, which will take some time as it is complicated. We can easily update the docs. Giving a hint that something will work in the future does not really help, does it?

[franzholz]

I think it helps to add the hint about the future for persons who are learning by reading the Docs. Then they get prepared already.

[CybotTM]

I think it helps to add the hint about the future for persons who are learning by reading the Docs. Then they get prepared already.

AFAIK there is not even a decision currently if it will be fixed.

[CybotTM]

The underlying issue should be resolved now with:

• Fix using escape chars phpDocumentor/guides#1312

But I don't know if and when
https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/Basics/RstCheatSheet.html#escape-characters
will be re-rendered with https://github.com/phpDocumentor/guides/releases/tag/1.9.6