Permit fenced code blocks with a language tag (#383)
The code block parser's hint and open regexes only matched a bare fence
followed immediately by a newline, so a fence with an info string such as
```js was never parsed as a code block. It fell through to inline parsing,
which dropped the raw fence markers and mangled braces in the code. Allow an
optional info string after the opening backticks (it is discarded, matching
the existing behavior of emitting a plain [code] block).
Co-authored-by: Spenser Black <me@spenser.black>
authored by