fix: make the workspace pass the CI lint/test gate

The new Gitea Actions build gate runs `cargo fmt --check`, `clippy -D warnings`,
and `cargo test` — stricter than the old deploy.sh, which only `cargo build`d.
That surfaced pre-existing drift that never compiled under the test/clippy
profile:

- apply rustfmt across the workspace (formatting only, no logic changes)
- moments-data: add the missing `prune_events` to the test-only `NoopWriter`
  stub (the EventWriter trait gained it with the blog-prune feature; a plain
  `cargo build` never compiles the `#[cfg(test)]` stub, so it went stale)
- moments-api: `.max().min()` -> `.clamp()`, and build `usvg::Options` with
  struct-update syntax instead of post-Default field assignment

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X7zF7Kf4JqDwa6M8Qgge9M

crates/moments-worker/src/main.rs

@@ -126,9 +126,7 @@ async fn main() -> anyhow::Result<()> {
     let store = Arc::new(PgStore::connect(&args.database_url).await?);
     store.migrate().await?;
 
-    let http = Client::builder()
-        .timeout(Duration::from_secs(30))
-        .build()?;
+    let http = Client::builder().timeout(Duration::from_secs(30)).build()?;
 
     let github = Arc::new(GithubSource::new(
         http.clone(),
@@ -250,8 +248,7 @@ async fn main() -> anyhow::Result<()> {
         tokio::spawn(async move { run_poller(github_repo, repo_interval).await });
     let gitea_task = tokio::spawn(async move { run_poller(gitea, gitea_interval).await });
     let hg_task = tokio::spawn(async move { run_poller(hg, hg_interval).await });
-    let bugzilla_task =
-        tokio::spawn(async move { run_poller(bugzilla, bugzilla_interval).await });
+    let bugzilla_task = tokio::spawn(async move { run_poller(bugzilla, bugzilla_interval).await });
     let blog_task =
         blog.map(|src| tokio::spawn(async move { run_poller(src, blog_interval).await }));