Revert "sentry: Enable tracing feature"

This reverts commit 43ac758.

Using `tracing_subscriber::fmt::layer()` disabled the `RUST_LOG` based env filter. But if we add the filter to the registry it basically disables the breadcrumb tracing for Sentry. https://docs.rs/tracing-subscriber/0.2.20/tracing_subscriber/layer/trait.Layer.html#filtering-with-layers has more information on this. Until we find a way to filter what the `fmt` subscriber prints without disabling the breadcrumbs for Sentry we should probably not use their `tracing` integration.

Author: Turbo87

Cargo.lock

@@ -74,7 +74,7 @@ rand = "0.8"
 reqwest = { version = "0.11", features = ["blocking", "gzip", "json"] }
 scheduled-thread-pool = "0.2.0"
 semver = { version = "1.0.3", features = ["serde"] }
-sentry = { version = "0.23.0", features = ["tracing"] }
+sentry = "0.23.0"
 serde = { version = "1.0.0", features = ["derive"] }
 serde_json = "1.0.0"
 sha2 = "0.9"

Cargo.toml

@@ -11,7 +11,6 @@ use sentry::{ClientOptions, IntoDsn};
 use std::io::Write;
 use tokio::io::AsyncWriteExt;
 use tokio::signal::unix::{signal, SignalKind};
-use tracing_subscriber::prelude::*;
 
 const CORE_THREADS: usize = 4;
 
@@ -34,10 +33,7 @@ fn main() -> Result<(), Box<dyn std::error::Error>> {
         });
 
     // Initialize logging
-    tracing_subscriber::registry()
-        .with(tracing_subscriber::fmt::layer())
-        .with(sentry::integrations::tracing::layer())
-        .init();
+    tracing_subscriber::fmt::init();
 
     let config = cargo_registry::config::Server::default();
     let env = config.env();