Remove CI system detection (#9643)

This was interesting when we were still routing the download traffic through our API servers, but this is no longer the case, so there is very little point in still running this detection for each request.

Author: Turbo87

.github/renovate.json5

@@ -62,7 +62,7 @@
             groupName: "diesel packages",
         },
         {
-            matchDepNames: ["aws-ip-ranges", "github-meta"],
+            matchDepNames: ["aws-ip-ranges"],
             automerge: true,
         },
         {

Cargo.lock

@@ -70,7 +70,6 @@ diesel_migrations = { version = "=2.2.0", features = ["postgres"] }
 dotenvy = "=0.15.7"
 flate2 = "=1.0.34"
 futures-util = "=0.3.31"
-github-meta = "=0.11.0"
 hex = "=0.4.3"
 http = "=1.1.0"
 http-body-util = "=0.1.2"

Cargo.toml

@@ -33,7 +33,6 @@ mod app;
 pub mod auth;
 pub mod boot;
 pub mod certs;
-pub mod ci;
 pub mod cloudfront;
 pub mod config;
 pub mod controllers;

src/ci.rs

@@ -1,7 +1,6 @@
 //! Log all requests in a format similar to Heroku's router, but with additional
 //! information that we care about like User-Agent
 
-use crate::ci::CiService;
 use crate::controllers::util::RequestPartsExt;
 use crate::headers::XRequestId;
 use crate::middleware::normalize_path::OriginalPath;
@@ -36,7 +35,6 @@ pub struct RequestMetadata {
     real_ip: Extension<RealIp>,
     user_agent: Option<TypedHeader<UserAgent>>,
     request_id: Option<TypedHeader<XRequestId>>,
-    ci_service: Option<CiService>,
 }
 
 pub async fn log_requests(
@@ -87,7 +85,6 @@ pub async fn log_requests(
         http.status_code = status.as_u16(),
         cause = response.extensions().get::<CauseField>().map(|e| e.0.as_str()).unwrap_or_default(),
         error.message = response.extensions().get::<ErrorField>().map(|e| e.0.as_str()).unwrap_or_default(),
-        ci = %request_metadata.ci_service.map(|ci| ci.to_string()).unwrap_or_default(),
         %custom_metadata,
         "{method} {url} → {status} ({duration:?})",
     );