Presence upsert can be immediately invisible for console-session requests

### Summary Console-session presence requests can intermittently fail to read a presence immediately after `PUT /v1/presences/:presenceId` returned 200. The failure affects the `console` project. The write response contains a presence, but the next list request can return `total: 0`, and a subsequent update using the returned ID can return 404. ### Exact reproduction Environment: - Appwrite server source: `18998d796847f1b228e3d8512fe6ae2969d464de` - PHP 8.5.9 - PHPUnit 12.5.33 - Kubernetes deployment - MySQL console/platform database - Redis cache - Dedicated project databases enabled From a clean deployment, warm the HTTP workers and run the Storage and Presences E2E directories serially: ```bash for round in 0 1 2; do for request in $(seq 1 50); do curl --silent --output /dev/null http://localhost/v1/health & done wait sleep 2 done vendor/bin/phpunit \ --display-incomplete \ --display-skipped \ --exclude-group abuseEnabled \ --exclude-group screenshots \ --exclude-group ciIgnore \ --exclude-group production \ --exclude-group provider-release \ tests/e2e/Services/Storage \ tests/e2e/Services/Presences ``` The run executed 143 tests and produced these four failures: ```text 1) PresenceConsoleClientTest::testListPresences Failed asserting that 0 is equal to 1 or is greater than 1. PresenceBase.php:271 2) PresenceConsoleClientTest::testUpdatePresenceSparseFields Failed asserting that 0 is equal to 1 or is greater than 1. PresenceBase.php:122 PresenceBase.php:518 3) PresenceConsoleClientTest::testUpdatePresenceNestedMetadata Failed asserting that 404 matches expected 200. PresenceBase.php:620 4) PresenceConsoleClientTest::testDeletePresence Failed asserting that 0 is equal to 1 or is greater than 1. PresenceBase.php:122 ``` The corresponding presence upserts returned 200. The failing helpers immediately listed or updated the just-upserted presence. This is intermittent: the same test class passed in isolation, and 20 serial repetitions pas…