Add unit tests and logging infrastructure for InMemory and RabbitMQ transports

- Implemented RecordingLogger and RecordingLoggerFactory for capturing log entries in tests.
- Added unit tests for InMemoryChannel, covering constructor behavior, property assignments, channel communication, and disposal.
- Created InMemoryTransportOptionsTests to validate default values and customizable options for InMemory transport.
- Developed RabbitMqFrameProtocolTests to ensure correct parsing and property creation for RabbitMQ frames.
- Added RabbitMqTransportOptionsTests to verify default settings and customization options for RabbitMQ transport.
- Updated project files for testing libraries and dependencies.

docs/modules/signals/evidence/README.md

@@ -29,22 +29,22 @@ Signed artifacts uploaded as workflow artifact `signals-dsse-signed-{run}` and o
 
 ## Development Signing (Local Testing)
 
-A development key pair is available for smoke tests:
+A development key pair is available for smoke tests. Recent dev bundles live under `docs/modules/signals/dev-smoke/2025-12-04/` and `docs/modules/signals/dev-smoke/2025-12-05/`.
 
 ```bash
 # Sign with dev key
 COSIGN_ALLOW_DEV_KEY=1 COSIGN_PASSWORD=stellaops-dev \
-  OUT_DIR=docs/modules/signals/dev-test \
+  OUT_DIR=docs/modules/signals/dev-smoke/2025-12-05 \
   tools/cosign/sign-signals.sh
 
 # Verify signature
 cosign verify-blob \
   --key tools/cosign/cosign.dev.pub \
-  --bundle docs/modules/signals/dev-test/confidence_decay_config.sigstore.json \
+  --bundle docs/modules/signals/dev-smoke/2025-12-05/confidence_decay_config.sigstore.json \
   docs/modules/signals/decay/confidence_decay_config.yaml
 ```
 
-**Note**: Dev key signatures are NOT suitable for Evidence Locker or production use.
+**Note**: Dev key signatures are NOT suitable for Evidence Locker or production use; tlog upload is disabled.
 
 ## Production Signing (Manual)