Update actix-web and tokio

Bumps [actix-rt](https://github.com/actix/actix-net) from 1.1.1 to 2.2.0.
- [Release notes](https://github.com/actix/actix-net/releases)
- [Commits](https://github.com/actix/actix-net/compare/rt-1.1.1...rt-v2.2.0)

Signed-off-by: dependabot[bot] <support@github.com>

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "hoc"
-version = "0.20.4"
+version = "0.18.0"
 authors = ["Valentin Brandl <vbrandl@riseup.net>"]
 edition = "2018"
 build = "build.rs"
@@ -13,34 +13,34 @@ path = "src/main.rs"
 name = "hoc"
 
 [dependencies]
-actix-rt = "2.5.0"
+actix-rt = "2.2.0"
 actix-web = "4.0.0-beta.8"
 badge = "0.3.0"
-bytes = "1.1.0"
+bytes = "1.0.1"
 config = { version = "0.11.0", features = ["toml"] }
 dotenv = "0.15.0"
-futures = "0.3.19"
+futures = "0.3.17"
-git2 = "0.13.25"
+git2 = "0.13.20"
 lazy_static = "1.4.0"
 number_prefix = "0.4.0"
 openssl-probe = "0.1.4"
-reqwest = "0.11.8"
+reqwest = "0.11.4"
-serde = "1.0.132"
+serde = "1.0.126"
-serde_derive = "1.0.130"
+serde_derive = "1.0.123"
-serde_json = "1.0.73"
+serde_json = "1.0.64"
-tracing = "0.1.29"
+tracing = "0.1.26"
-tracing-actix-web = "0.5.0-beta.1"
+tracing-actix-web = "0.4.0-beta.11"
-tracing-bunyan-formatter = "0.3.1"
+tracing-bunyan-formatter = "0.2.4"
 tracing-futures = "0.2.5"
 tracing-log = "0.1.2"
-tracing-subscriber = { version = "0.3.5", features = ["registry", "env-filter"] }
+tracing-subscriber = { version = "0.2.19", features = ["registry", "env-filter"] }
 
 [build-dependencies]
 ructe = "0.13.4"
-vergen = { version = "6.0.0", default-features = false, features = ["git"] }
+vergen = { version = "5.1.13", default-features = false, features = ["git"] }
 
 [dev-dependencies]
-awc = "3.0.0-beta.10"
+awc = "3.0.0-beta.7"
 ructe = "0.13.4"
 tempfile = "3.2.0"
-tokio = "1.15.0"
+tokio = "1.11.0"

README.md

@@ -19,8 +19,8 @@ The API is as simple as
 https://<host>/<service>/<user>/<repo>
 ```
 
-where `<service>` is one of `gitub`, `gitlab`, `bitbucket` or `sourcehut`. The HoC data can also be received as JSON by
+where `<service>` is one of `gitub`, `gitlab` or `bitbucket`. The HoC data can also be received as JSON by appending
-appending `/json` to the reuqest path:
+`/json` to the reuqest path:
 
 ```
 https://<host>/<service>/<user>/<repo>/json