docs: 💄 use rich for pretty output in guide docs (#259)

# Description

Needs a quick review
Closes #238

Make output easier to read, esp larger objects like dictionaries. This
adds both coloring and formatting. See commit messages for more details.

## Checklist

- [x] Ran `just run-all`
- I'm seeing some failure checking typos on a JS method in an HTML file,
but that is probably not related to this PR... (maybe the built doc
pages are not properly excluded from the typo check?)

Co-authored-by: Luke W. Johnston <lwjohnst86@users.noreply.github.com>

Author: joelostblom

docs/guide/check.qmd

@@ -5,6 +5,8 @@ jupyter: python3
 order: 1
 ---
 
+{{< include ../includes/_pretty_repr.qmd >}}
+
 The purpose of `check-datapackage` is to make sure a Data Package's
 metadata---stored in its `datapackage.json` file---complies with the
 [Data Package standard](https://datapackage.org). This standard defines
@@ -48,11 +50,9 @@ format. The example looks like this (from the
 
 ```{python}
 import check_datapackage as cdp
-import pprint
-
 
 package_properties = cdp.example_package_properties()
-pprint.pp(package_properties)
+package_properties
 ```
 
 When we call `check()` on these properties, it returns an empty list:

docs/guide/config.qmd

@@ -5,6 +5,8 @@ jupyter: python3
 order: 3
 ---
 
+{{< include ../includes/_pretty_repr.qmd >}}
+
 You can pass a [`Config`](/docs/reference/Config.qmd) object to
 [`check()`](/docs/reference/check.qmd) to customise the checks done on
 your Data Package's properties. The following configuration options are
@@ -40,7 +42,6 @@ the `required` check by defining an `Exclusion` object with this `type`:
 
 ```{python}
 from textwrap import dedent
-import pprint
 import check_datapackage as cdp
 
 exclusion_required = cdp.Exclusion(type="required")
@@ -90,7 +91,7 @@ package_properties = cdp.example_package_properties()
 package_properties["name"] = 123
 package_properties["created"] = "not-a-date"
 package_properties["resources"][0]["path"] = "\\not/a/path"
-pprint.pp(package_properties)
+package_properties
 ```
 
 When we run `check()` on these properties, we get the three expected issues:

docs/guide/issues.qmd

@@ -5,6 +5,8 @@ jupyter: python3
 order: 2
 ---
 
+{{< include ../includes/_pretty_repr.qmd >}}
+
 ## The `Issue` class
 
 One `Issue` corresponds to one failed check on one field in the

docs/includes/_pretty_repr.qmd

@@ -0,0 +1,8 @@
+<!-- Make output representation of code objects easier to read-->
+
+```{python}
+#| include: false
+from rich import pretty
+
+pretty.install()
+```