Remove tracing-log dependency and related initialization from logging setup

- Eliminated the `tracing-log` crate from `Cargo.toml` and `Cargo.lock`, streamlining the logging configuration.
- Updated the logging initialization function to remove the `tracing_log::LogTracer::init()` call, simplifying the logging setup process.

These changes aim to enhance the logging system by reducing unnecessary dependencies and improving code clarity.

Cargo.lock

@@ -255,7 +255,6 @@ dependencies = [
  "toml",
  "tracing",
  "tracing-appender",
- "tracing-log",
  "tracing-subscriber",
  "uuid",
  "walkdir",

Cargo.toml

@@ -101,7 +101,6 @@ thiserror = "2"
 tokio = { version = "1.49.0", features = ["rt", "rt-multi-thread", "macros", "sync"] }
 tracing = "0.1"
 tracing-appender = "0.2"
-tracing-log = "0.2"
 tracing-subscriber = { version = "0.3", features = ["env-filter", "fmt", "time"] }
 uuid = { version = "1.21.0", features = ["v4", "serde"] }
 clap = { version = "4", features = ["derive"] }

src/logging.rs

@@ -23,8 +23,6 @@ pub fn init_logging(
     file_log_level: Option<tracing::level_filters::LevelFilter>,
     command_name: &str,
 ) -> LogGuard {
-    tracing_log::LogTracer::init().expect("Failed to set log tracer");
-
     let console_filter = match verbosity {
         0 => "info",
         1 => "info,librojo=debug",