fix(ci): gate event crate doctest behind mem feature and apply rustfmt

The crate-root doctest used InMemoryEventBus/TypedEventBus (gated behind
the 'mem' feature), so `cargo test -p mytheclipse-event --no-default-features
--features amqp|nats` failed to compile the doctest (E0432). The example is
now no_run with the mem-dependent imports inside a #[cfg(feature="mem")]
main, so it compiles (and runs) when mem is on and degrades to an empty main
when off.

Also apply rustfmt to mytheclipse-config/dynamic.rs and
mytheclipse-storage/{gcs,s3}.rs to satisfy cargo fmt --all --check.

crates/mytheclipse-config/src/dynamic.rs

@@ -49,7 +49,10 @@ impl<T: Config + Clone> DynamicConfig<T> {
 
     /// Replaces the current value and notifies subscribers.
     pub fn set(&self, new: T) {
-        *self.inner.write().expect("mytheclipse-config: RwLock poisoned") = new;
+        *self
+            .inner
+            .write()
+            .expect("mytheclipse-config: RwLock poisoned") = new;
         let _ = self.tx.send(());
     }