Don't we need to change from create() to create_async() in this file?

       let _mock = server
            .mock("GET", "/hello")
            .match_header("Authorization", "Bearer test-token")
            .with_status(204)
            .create(); // shouldn't it be `.create_async().await;`   ?

Looking at the crate documentation, there doesn't seem to be much difference between the two, i.e. both will work here, but using .create_async we don't block and await, which would maybe have performance implications when registering many mocks, but in our use case there's no difference as long as .create also works so the difference is if we started any other tasks before, calling .create() would block the only worker thread and block these tasks as well, but only for a short time that it takes to register a mock, so there's not much difference in our case.

Nevermind, didn't read the whole thing, it seems blocking the runtime for any amount of time is a hard error somehow.
From mockito's docs:

Mockito comes with both a sync and an async interface.

In order to write async tests, you’ll need to use the _async methods:

• Server::new_async
• Server::new_with_opts_async
• Mock::create_async
• Mock::assert_async
• Mock::matched_async
• Mock::remove_async

…otherwise your tests will not compile and you’ll see the following error:

Cannot block the current thread from within a runtime.
This happens because a function attempted to block the current thread while the thread is being used to drive asynchronous tasks.

In this case you're right, we need to use .create_async() everywhere

Thanks @Bravo555 for the insight. However, I decided to apply @rina23q suggestions to be consistent.

typo: there's two spaces in task panicked

The whole commit has been dropped

You missed to apply create_async to the line below. (line 899)

:-) I will fixed that.

That said this demonstrates that @Bravo555 comment is correct. The tests are working as expected with create() as well ass with create_async().