cargo: switch from proc-macro pin-project to declarative pin-project-lite

In our simple use cases they both should generate the same code, see
[0] for notable differences. While we cannot drop proc-macro due to
that switch, all of our dependencies that use pinning already use
pin-project-lite, so this allows us to drop a whole crate in general
while not loosing anything.

[0]: https://github.com/taiki-e/pin-project-lite#pin-project-vs-pin-project-lite

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

pbs-client/src/vsock_client.rs

@@ -8,7 +8,7 @@ use http::{Request, Response};
 use hyper::client::connect::{Connected, Connection};
 use hyper::client::Client;
 use hyper::Body;
-use pin_project::pin_project;
+use pin_project_lite::pin_project;
 use serde_json::Value;
 use tokio::io::{AsyncRead, AsyncWrite, AsyncWriteExt, ReadBuf};
 use tokio::net::UnixStream;
@@ -20,11 +20,12 @@ pub const DEFAULT_VSOCK_PORT: u16 = 807;
 #[derive(Clone)]
 struct VsockConnector;
 
-#[pin_project]
-/// Wrapper around UnixStream so we can implement hyper::client::connect::Connection
-struct UnixConnection {
-    #[pin]
-    stream: UnixStream,
+pin_project! {
+    /// Wrapper around UnixStream so we can implement hyper::client::connect::Connection
+    struct UnixConnection {
+        #[pin]
+        stream: UnixStream,
+    }
 }
 
 impl tower_service::Service<Uri> for VsockConnector {