refactor(tests-async): unify duplicated tokio runtime bridges

11 downloader/installer integration-test files each redefined an
identical current_thread `run()` helper to block on async code. Extract
one shared multi_thread Runtime into tests/common/async_runtime.rs so
concurrent #[test] threads can all block_on it, matching the direction
item 7 (top-level Runtime) will take in production code.

1 files changed, 1 insertions, 7 deletions

diff --git a/crates/shirabe/tests/downloader/perforce_downloader_test.rs b/crates/shirabe/tests/downloader/perforce_downloader_test.rs
index 13a818a6..bdf24a2e 100644
--- a/crates/shirabe/tests/downloader/perforce_downloader_test.rs
+++ b/crates/shirabe/tests/downloader/perforce_downloader_test.rs
@@ -1,5 +1,6 @@
 //! ref: composer/tests/Composer/Test/Downloader/PerforceDownloaderTest.php
 
+use crate::async_runtime::run;
 use crate::io_mock::{Expectation, get_io_mock};
 use crate::io_stub::IOStub;
 use crate::process_executor_mock::get_process_executor_mock;
@@ -42,13 +43,6 @@ mockall::mock! {
     }
 }
 
-fn run<F: std::future::Future>(future: F) -> F::Output {
-    tokio::runtime::Builder::new_current_thread()
-        .build()
-        .unwrap()
-        .block_on(future)
-}
-
 /// ref: PerforceDownloaderTest::getConfig (seeds `home` with the temp dir)
 fn get_config(test_path: &std::path::Path) -> Config {
     let mut config = Config::new(true, None);