Integrate linecount analysis in publish controller

This modifies the publish endpoint to extract and store linecount statistics by extracting linecount data from tarball processing results and serializing the stats to `JSON` for database storage. The linecount data is then passed to the `NewVersion` builder for persistence.

All publish-related test snapshots are updated to include linecount data, demonstrating that the integration works correctly across various publish scenarios. The implementation maintains backward compatibility with null linecount values for any edge cases.

Author: Turbo87

src/controllers/krate/publish.rs

@@ -26,7 +26,7 @@ use sha2::{Digest, Sha256};
 use std::collections::HashMap;
 use tokio::io::{AsyncRead, AsyncReadExt};
 use tokio_util::io::StreamReader;
-use tracing::{error, instrument};
+use tracing::{error, instrument, warn};
 use url::Url;
 
 use crate::models::{
@@ -482,6 +482,10 @@ pub async fn publish(app: AppState, req: Parts, body: Body) -> AppResult<Json<Go
         // Read tarball from request
         let hex_cksum: String = Sha256::digest(&tarball_bytes).encode_hex();
 
+        let linecounts = serde_json::to_value(tarball_info.linecount_stats)
+            .inspect_err(|err| warn!("Failed to convert linecounts to serde_json::Value: {err}"))
+            .ok();
+
         // Persist the new version of this crate
         let new_version = NewVersion::builder(krate.id, &version_string)
             .features(serde_json::to_value(&features)?)
@@ -502,6 +506,7 @@ pub async fn publish(app: AppState, req: Parts, body: Body) -> AppResult<Json<Go
             .maybe_repository(repository.as_deref())
             .categories(&categories)
             .keywords(&keywords)
+            .maybe_linecounts(linecounts)
             .build();
 
         let version = new_version.save(conn).await.map_err(|error| {