Add new chapter for Error Reporting (#21)

* Draft first part of error reporting

* Finish drafting error reporting

Author: soareschen

Cargo.lock

@@ -9,4 +9,5 @@ serde = {version = "1", features = ["derive"] }
 itertools = "0.11.0"
 serde_json = "1"
 anyhow = "1"
-datetime = "0.5.2"
+datetime = "0.5.2"
+sha1 = "0.10.6"

Cargo.toml

@@ -22,8 +22,9 @@
 
 - [Associated Types](associated-types.md)
 - [Error Handling](error-handling.md)
-    - [Delegated Error Raiser](delegated-error-raiser.md)
-    - [Detailed Error Reporting]()
+    - [Delegated Error Raisers](delegated-error-raiser.md)
+    - [Error Reporting](error-reporting.md)
+    - [Wrapping Errors]()
 - [Component Presets]()
 - [Trait-Generic Providers]()
     - [`WithProvider`]()

content/SUMMARY.md

@@ -1,4 +1,4 @@
-# Delegated Error Raiser
+# Delegated Error Raisers
 
 In the previous chapter, we have defined context-generic error raisers like `RaiseFrom`
 and `DebugAsAnyhow`, which can be use to raise any source error that satisfy certain
@@ -13,7 +13,7 @@ For example, we may want to use `RaiseFrom` when there is a `From` instance, and
 In this chapter, we will cover the `UseDelegate` pattern, which offers a declarative
 way to handle errors differently depending on the source error type.
 
-## Ad Hoc Error Raiser
+## Ad Hoc Error Raisers
 
 One way that we can handle source errors differently is by defining an error raiser
 provider that has explicit implementation for each source error, such as follows: