[BUG] Inline code not escaping blocks of back ticks.

[SSlinky]

Two or more back ticks should not be interpreted as inline code markers / fences. They should be parsed literally as either normal text or inline code, depending on where the single back ticks are.

To Reproduce
Steps to reproduce the behavior:

1. Create a markdown file that includes a block of two or more back ticks inside inline code.
   e.g. Some inline code with ```` ticks present.
2. Run the parser.

Expected behavior
Three inline text blocks created with styles normal, inline code, normal, respectively.
Text content is "Some ", "inline code with ```` ticks", and " present." respectively.

Additional context
The root cause is the RegEx pattern that finds inline code.

[SSlinky]

Current pattern is:

([^\\`](?:\\\\)*)(`)((?:[^`\n]+?))(`)

[SSlinky]

Back ticks should not be escaped. This is a feature. Code fences here should match exactly, i.e. the close fence must be the same number of back ticks as the open.