Add function and tests for markdown chunks using pygment langs like {.py and {.python etc

[chrimaho]

Closes #281

[adamchainz]

There’s quite a lot of overlap here with #239, the MyST support. I will defer a proper review for now since I want to dive into understanding both formats to understand how to keep things easy to understand.

[chrimaho]

The full regex in the MD_RE variable reads:

(?P<before>^(?P<indent> *)```\s*(\{?\s*)?(\.?)?(python|py|sage|python3|py3|numpy)( .*?)?\n)(?P<code>.*?)(?P<after>^(?P=indent)```\s*$)

If you plug this in to https://regex101.com/, it will give you the following explanation for the 3rd and 4th capture group:

3rd Capturing Group (\{?\s*)?

• \{ matches the character { with index 123₁₀ (7B₁₆ or 17₃₈) literally (case sensitive)
  ? matches the previous token between zero and one times, as many times as possible, giving back as needed (greedy)
• \s matches any whitespace character (equivalent to [\r\n\t\f\v ])
  * matches the previous token between zero and unlimited times, as many times as possible, giving back as needed (greedy)
• ? matches the previous token between zero and one times, as many times as possible, giving back as needed (greedy)

4th Capturing Group (\.?)?

• \. matches the character . with index 46₁₀ (2E₁₆ or 56₈) literally (case sensitive)
  ? matches the previous token between zero and one times, as many times as possible, giving back as needed (greedy)
• ? matches the previous token between zero and one times, as many times as possible, giving back as needed (greedy)

This should now meet the needs of both MyST and the Pygment langs used in pymdown-extensions.

[chrimaho]

Hi @adamchainz, just wondering if there is anything else that I can do to support this PR?