Random CI failures in speed_check test

[Nutomic]

https://woodpecker.join-lemmy.org/repos/129/pipeline/13438/14#L1220

---- impls::tests::speed_check stdout ----
🧮 updating database statistics
Elapsed: 85ms
thread 'impls::tests::speed_check' panicked at crates/db_views_post/src/impls.rs:1984:5:
Query took 85ms, longer than the max of 80ms
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: lemmy_db_views_post::impls::tests::__test_context_wrapped_speed_check::{{closure}}
   3: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::future::future::Future>::poll
   4: <futures_util::future::future::catch_unwind::CatchUnwind<Fut> as core::future::future::Future>::poll::{{closure}}
   5: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
   6: std::panicking::try::do_call
   7: __rust_try
   8: std::panic::catch_unwind
   9: <futures_util::future::future::catch_unwind::CatchUnwind<Fut> as core::future::future::Future>::poll
  10: lemmy_db_views_post::impls::tests::speed_check::{{closure}}::{{closure}}
  11: <core::pin::Pin<P> as core::future::future::Future>::poll
  12: <core::pin::Pin<P> as core::future::future::Future>::poll
  13: tokio::runtime::scheduler::current_thread::CoreGuard::block_on::{{closure}}::{{closure}}::{{closure}}
  14: tokio::runtime::scheduler::current_thread::CoreGuard::block_on::{{closure}}::{{closure}}
  15: tokio::runtime::scheduler::current_thread::Context::enter
  16: tokio::runtime::scheduler::current_thread::CoreGuard::block_on::{{closure}}
  17: tokio::runtime::scheduler::current_thread::CoreGuard::enter::{{closure}}
  18: tokio::runtime::context::scoped::Scoped<T>::set
  19: tokio::runtime::context::set_scheduler::{{closure}}
  20: std::thread::local::LocalKey<T>::try_with
  21: std::thread::local::LocalKey<T>::with
  22: tokio::runtime::context::set_scheduler
  23: tokio::runtime::scheduler::current_thread::CoreGuard::enter
  24: tokio::runtime::scheduler::current_thread::CoreGuard::block_on
  25: tokio::runtime::scheduler::current_thread::CurrentThread::block_on::{{closure}}
  26: tokio::runtime::context::runtime::enter_runtime
  27: tokio::runtime::scheduler::current_thread::CurrentThread::block_on
  28: tokio::runtime::runtime::Runtime::block_on_inner
  29: tokio::runtime::runtime::Runtime::block_on
  30: lemmy_db_views_post::impls::tests::speed_check::{{closure}}
  31: core::ops::function::FnOnce::call_once
  32: serial_test::serial_code_lock::local_serial_core_with_return
  33: lemmy_db_views_post::impls::tests::speed_check
  34: lemmy_db_views_post::impls::tests::speed_check::{{closure}}
  35: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

cc @dullbananas

[dessalines]

I think the easiest thing for now would just be to raise the limit. When its running on my slower CI machines, it sometimes fails.

We still do need speed checks in the CI, but doing that should come as a part of #5555