Convert all code listings to use new <Listing> preprocessor

[chriskrycho]

As of #3918, we have a preprocessor that allows us to author with a custom HTML tag, Listing, roughly as if it were a component in a templating language. This input:

<Listing number="1-1" file-name="src/lib.rs" caption="A listing showing how to use a `Listing`">

```rust
fn main() {
    println!("Hello, listing!");
}
```

</Listing>

…will generate this output in the regular book (and strip all the tags in the NoStarch book):

<figure class="listing">
<span class="file-name">Filename: src/lib.rs</span>
<pre><pre class="playground"><code class="language-rust">fn main() {
    println!("Hello, listing!");
}</code></pre></pre>
<figcaption>Listing 1-2: A listing showing how to use a <code>Listing</code></figcaption>
</figure>

As described in the PR adding support for this, the result is more accessible HTML, which will also give us a nice way to hook in for styling things better if we so choose.

---

If you’d like to help, please leave a comment below noting which chapter you’d like to pick up so folks don’t do duplicate work! If it already has a user handle by it, please don’t work on that chapter.

Note for contributors: when converting to a <Listing>, you can drop the leading Listing <number>: from the caption arg, since it handles that automatically with the number arg.

• Chapter 1 (@davidkurilla)
• Chapter 2 (@davidkurilla)
• Chapter 3 (@davidkurilla)
• Chapter 4
• Chapter 5
• Chapter 6 (@SpectralPixel)
• Chapter 7 (@SpectralPixel)
• Chapter 8 (@SpectralPixel)
• Chapter 9 (@SpectralPixel)
• Chapter 10 (@SpectralPixel)
• Chapter 11
• Chapter 12
• Chapter 13
• Chapter 14
• Chapter 15
• Chapter 16
• Chapter 17
• Chapter 18
• Chapter 19
• Chapter 20

[davidkurilla]

I'd like to help with chapter 1.

[davidkurilla]

Thanks for the feedback for my pervious contribution! I plan to work on converting chapters 2 and 3

[chriskrycho]

Very good! Thank you! 💙

[SpectralPixel]

I'll do chapters 6-10. Already working on it.