Expose underlying error when peer_connect attestation fails (#46)

### TL;DR

Improved error logging for attestation creation failures in the ChatterServer.
a the attestation creation code in the `ChatterService` implementation to use a match statement instead of an if-let pattern. This change allows for capturing and logging the specific error that occurs during attestation creation, rather than just logging a generic error message.

### How to test?

1. Run a Lit node in an environment where attestation creation might fail
2. Check the logs for more detailed error messages that now include the specific error information
3. Verify that the error message format is now `"Error creating attestation: {:?}"` with the actual error details

### Why make this change?

This change enhances debugging capabilities by providing more detailed error information when attestation creation fails. Having the specific error details in the logs will make it easier to diagnose and fix issues related to attestation creation in production environments.

Author: Garandor

rust/lit-node/lit-node/src/p2p_comms/web/chatter_server.rs

@@ -198,11 +198,14 @@ impl ChatterService for ChatterServer {
             version: version::get_version().to_string(),
         };
 
-        if let Ok(at) = create_attestation(cfg.load_full(), &noonce, None).await {
-            peer_item.attestation = Some(at);
-        } else {
-            #[cfg(not(feature = "testing"))]
-            error!("Error creating attestation.");
+        match create_attestation(cfg.load_full(), &noonce, None).await {
+            Ok(at) => {
+                peer_item.attestation = Some(at);
+            }
+            Err(e) => {
+                #[cfg(not(feature = "testing"))]
+                error!("Error creating attestation: {:?}", e);
+            }
         }
 
         let peer_item_json = match serde_json::to_string(&peer_item) {