core: Remove view cleanup trace logs (#5137)

Those were introduced at info level to debug apparent deadlocking
issues, which turned out to be unrelated. They generate quite a bit of
noise.

Removing them instead of lowering the level as we already have
sufficient logging around view cleanup.

# Expected complexity level and risk

1

# Testing

Logging only.

Author: kim

crates/core/src/db/relational_db.rs

@@ -6,7 +6,6 @@ use crate::util::asyncify;
 use crate::worker_metrics::WORKER_METRICS;
 use anyhow::{anyhow, Context};
 use enum_map::EnumMap;
-use log::info;
 use spacetimedb_commitlog::repo::OnNewSegmentFn;
 use spacetimedb_commitlog::{self as commitlog, Commitlog, SizeOnDisk};
 use spacetimedb_data_structures::map::HashSet;
@@ -1110,15 +1109,13 @@ pub fn spawn_view_cleanup_loop(db: Arc<RelationalDB>) -> tokio::task::AbortHandl
             // in milliseconds, which may be too long for async tasks.
             let db = db.clone();
             let db_identity = db.database_identity();
-            info!("running view cleanup for database {db_identity}");
             tokio::task::spawn_blocking(move || run_view_cleanup(&db))
                 .await
                 .inspect_err(|e| {
                     log::error!("[{}] DATABASE: failed to run view cleanup task: {}", db_identity, e);
                 })
                 .ok();
 
-            info!("pausing view cleanup for database {db_identity}");
             tokio::time::sleep(VIEWS_EXPIRATION).await;
         }
     })