fix: use docker stop instead of docker kill for Redis-Destructive tests

docker kill sends SIGKILL which prevents Redis from clean shutdown,
causing ~18 minute delays in test recovery. docker stop sends SIGTERM
for graceful shutdown, matching the main branch behavior.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: abnegate

tests/e2e/Adapter/Scopes/GeneralTests.php

@@ -373,7 +373,7 @@ public function testCacheFallback(): void
         // Bring down Redis
         $stdout = '';
         $stderr = '';
-        Console::execute('docker ps -a --filter "name=utopia-redis" --format "{{.Names}}" | xargs -r docker kill', '', $stdout, $stderr);
+        Console::execute('docker ps -a --filter "name=utopia-redis" --format "{{.Names}}" | xargs -r docker stop', '', $stdout, $stderr);
 
         // Check we can read data still
         $this->assertCount(1, $database->find('testRedisFallback', [Query::equal('string', ['text📝'])]));
@@ -443,7 +443,7 @@ public function testCacheReconnect(): void
             // Bring down Redis
             $stdout = '';
             $stderr = '';
-            Console::execute('docker ps -a --filter "name=utopia-redis" --format "{{.Names}}" | xargs -r docker kill', '', $stdout, $stderr);
+            Console::execute('docker ps -a --filter "name=utopia-redis" --format "{{.Names}}" | xargs -r docker stop', '', $stdout, $stderr);
             sleep(1);
 
             // Restart Redis containers