io: use io_uring for all io

There should no longer be any

- read
- write
- connect
- sendmsg
- recvmsg
- accept

calls in the codebase. Previously we were using a mix of io_uring and
these calls which had some negative effects: Since we were using the old
system calls, we had to set the file descriptors to non-blocking. But
our io_uring code did not handle EAGAIN. This lead to programs sometimes
being killed when the wayland IO was actually blocking.

Now all file descriptors are set to blocking, but io_uring makes it
non-blocking from our perspective. The one exception are evdev files
because they are read via libinput and libinput uses the old system
calls.

src/cli/seat_test.rs

@@ -2,7 +2,7 @@ use {
     crate::{
         cli::{GlobalArgs, SeatTestArgs},
         ifs::wl_seat::wl_pointer::{PendingScroll, CONTINUOUS, FINGER, WHEEL},
-        tools::tool_client::{Handle, ToolClient},
+        tools::tool_client::{with_tool_client, Handle, ToolClient},
         wire::{
             jay_compositor::{GetSeats, Seat, SeatEvents},
             jay_seat_events::{
@@ -16,13 +16,14 @@ use {
 };
 
 pub fn main(global: GlobalArgs, args: SeatTestArgs) {
-    let tc = ToolClient::new(global.log_level.into());
-    let screenshot = Rc::new(SeatTest {
-        tc: tc.clone(),
-        args,
-        names: Default::default(),
+    with_tool_client(global.log_level.into(), |tc| async move {
+        let screenshot = Rc::new(SeatTest {
+            tc: tc.clone(),
+            args,
+            names: Default::default(),
+        });
+        run(screenshot).await;
     });
-    tc.run(run(screenshot));
 }
 
 struct SeatTest {