Request: Disable Discord RPC when Discord is not running or installed, plus disable replaycollector feature

[HikariCalyx]

1. If Discord is not installed or running on PC for whatever reason (e.g. Discord is blocked in specific country or region), the log will be spammed by Discord RPC error:

[2025-10-08T11:55:51Z WARN  tango::discord] did not open discord RPC client: could not connect
    
    Stack backtrace:
       0: std::backtrace::Backtrace::create
       1: std::backtrace::Backtrace::capture
       2: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
       3: tango::discord::Client::new::{{closure}}
       4: tokio::runtime::task::core::Core<T,S>::poll
       5: tokio::runtime::task::harness::Harness<T,S>::poll
       6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
       7: tokio::runtime::scheduler::multi_thread::worker::Context::run
       8: tokio::runtime::context::scoped::Scoped<T>::set
       9: tokio::runtime::context::runtime::enter_runtime
      10: tokio::runtime::scheduler::multi_thread::worker::run
      11: tokio::runtime::task::core::Core<T,S>::poll
      12: tokio::runtime::task::harness::Harness<T,S>::poll
      13: tokio::runtime::blocking::pool::Inner::run
      14: std::sys::backtrace::__rust_begin_short_backtrace
      15: core::ops::function::FnOnce::call_once{{vtable.shim}}
      16: std::sys::pal::windows::thread::Thread::new::thread_start
      17: <unknown>
      18: <unknown>

2. Current replay collector server ( replaycollector.tango.n1gp.net ) used by Tango cannot be connected due to DNS resolving failure, and crashed Tango.

[2025-10-08T12:07:58Z ERROR tango::session] failed to submit replay: error sending request for url (https://replaycollector.tango.n1gp.net/): error trying to connect: dns error: No such host is known. (os error 11001)
    
    Caused by:
        0: error trying to connect: dns error: No such host is known. (os error 11001)
        1: dns error: No such host is known. (os error 11001)
        2: No such host is known. (os error 11001)
    
    Stack backtrace:
       0: std::backtrace::Backtrace::create
       1: std::backtrace::Backtrace::capture
       2: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
       3: tango::session::Session::new_pvp::{{closure}}::{{closure}}
       4: tokio::runtime::task::core::Core<T,S>::poll
       5: tokio::runtime::task::harness::Harness<T,S>::poll
       6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
       7: tokio::runtime::scheduler::multi_thread::worker::Context::run
       8: tokio::runtime::context::scoped::Scoped<T>::set
       9: tokio::runtime::context::runtime::enter_runtime
      10: tokio::runtime::scheduler::multi_thread::worker::run
      11: tokio::runtime::task::core::Core<T,S>::poll
      12: tokio::runtime::task::harness::Harness<T,S>::poll
      13: tokio::runtime::blocking::pool::Inner::run
      14: std::sys::backtrace::__rust_begin_short_backtrace
      15: core::ops::function::FnOnce::call_once{{vtable.shim}}
      16: std::sys::pal::windows::thread::Thread::new::thread_start
      17: <unknown>
      18: <unknown>

[ArthurCose]

1. I'll see about fixing this
2. Are there logs after that, and does it ever show up without crashing? This matches up with a block containing: log::error!("failed to submit replay: {:?}", e);, which eats the error and logs instead of crashing. I'm thinking this log may be unrelated to the crash.

Also, I'd recommend opening two issues for two unrelated problems in the future, as it makes it easier to figure out what is fixed and confusing overlapping conversations.

[HikariCalyx]

1. I'll see about fixing this
2. Are there logs after that, and does it ever show up without crashing? This matches up with a block containing: log::error!("failed to submit replay: {:?}", e);, which eats the error and logs instead of crashing. I'm thinking this log may be unrelated to the crash.

Also, I'd recommend opening two issues for two unrelated problems in the future, as it makes it easier to figure out what is fixed and confusing overlapping conversations.

After filling out discord RPC error spam, I only see these issues, but probably irrelevant:

[2025-10-08T12:26:24Z ERROR tango::patch] failed to update patches: deadline has elapsed    Stack backtrace:
       0: std::backtrace::Backtrace::create
       1: std::backtrace::Backtrace::capture
       2: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
       3: tokio::runtime::park::CachedParkThread::block_on
       4: tango::sync::block_on
       5: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
       6: tokio::runtime::task::core::Core<T,S>::poll
       7: tokio::runtime::task::harness::Harness<T,S>::poll
       8: tokio::runtime::blocking::pool::Inner::run
       9: std::sys::backtrace::__rust_begin_short_backtrace
      10: core::ops::function::FnOnce::call_once{{vtable.shim}}
      11: std::sys::pal::windows::thread::Thread::new::thread_start
      12: <unknown>
      13: <unknown>
[2025-10-08T12:26:24Z INFO  tango::patch] patch autoupdate completed

<did not open discord RPC client messages>

exit status: ExitStatus(ExitStatus(3489660927))