fix: address CI lint and clarify worker-exit log

- update concurrent worker exit warning per review nit
- drop redundant .cloned() in ApiGatewayV2 cookies mapping
  (clippy lint was pre-existing and unrelated to this PR)

Author: alessandrobologna

lambda-http/src/response.rs

@@ -97,7 +97,6 @@ impl LambdaResponse {
                 let cookies = headers
                     .get_all(SET_COOKIE)
                     .iter()
-                    .cloned()
                     .map(|v| v.to_str().ok().unwrap_or_default().to_string())
                     .collect();
                 headers.remove(SET_COOKIE);

lambda-runtime/src/runtime.rs

@@ -209,10 +209,13 @@ where
                 Ok(Ok(())) => {
                     // `concurrent_worker_loop` runs indefinitely, so an Ok return indicates
                     // an unexpected worker exit; we still decrement because the task is gone.
-                    warn!(remaining_workers, "Concurrent worker exited unexpectedly without error");
+                    warn!(
+                        remaining_workers,
+                        "Concurrent worker exited cleanly (unexpected - loop should run forever)"
+                    );
                     if first_error.is_none() {
                         first_error = Some(Box::new(io::Error::other(
-                            "all concurrent workers exited unexpectedly without error",
+                            "all concurrent workers exited cleanly (unexpected - loop should run forever)",
                         )));
                     }
                 }