[Bug] Fixes and Enhancements for Code Block Tracking

[ryul1206]

This bug has been fixed and will be included in version 2.0.

• Fixed bug 1: Enhanced End-of-Code-Block Detection

  It is safe to ignore command tags in the code block (or inline code). However, in version 1.x, the line marking the end of the code block was not recognized as part of the code block. This presents a risk of parsing command tags that could exist on the last line of the code block.

  | Lorem ipsum dolor `sit amet,         | Code block O
  | consectetur adipiscing elit.         | Code block O
  | Praesent auctor eu` neque et varius. | Code block X -> Now O
  

• Fixed bug 2: Improved Inline Code Recognition

  Inline code can span multiple lines, but if there is an empty line, it should be recognized as regular text. However, in version 1.x, even if there was an empty line, it was mistakenly recognized as a code section.

  | Lorem ipsum dolor `sit amet,         | Code block O -> Now X
  |                                      | Code block O -> Now X
  | Praesent auctor eu` neque et varius. | Code block X
  

• Fixed bug 3: Distinguished Between Inline Code and Code Blocks

  Three backticks can be used to create both code blocks and inline code, but version 1.x was unable to distinguish between them. We have made modifications to differentiate between the two. Code blocks now take precedence over inline code.

  | Lorem ipsum dolor ```sit amet,       | Code block O -> Now X
  | ```                                  | Code block X -> Now O
  | Praesent auctor eu` neque et varius. | Code block X -> Now O