ci(e2e): bump logoscore daemon+CLI past the QtRO reply-wedge fix (#58)

Root-caused #58/#59 to the pre-fix ModuleProxy in the e2e daemon's SDK: it
emits module events directly on the caller's (module FFI) thread, racing QtRO
source serialization against an in-flight reply and permanently wedging the
sync-reply channel. Fixed upstream in logos-cpp-sdk d77c3dd (marshal events
onto the source thread) + logos-protocol #7 (defer async completion off the
QtRO read stack). Our daemon was pinned 6 commits before it.

Bump the smoke-image daemon (logoscore-py aa45db52 -> 71e00381) and the CLI
(logoscore-cli 5a1cf746 -> a9e18455) to a post-split closure carrying both
fixes. The Python client already floats logoscore@master, so no requirements
change is needed.

.github/workflows/ci.yml

@@ -70,14 +70,14 @@ jobs:
         run: |
           git clone https://github.com/logos-co/logos-logoscore-py.git /tmp/logoscore-py
           cd /tmp/logoscore-py
-          git checkout aa45db52
+          git checkout 71e003813a8633e9efadaf6ab66a6b0615dcc0f5
           bash tests/docker_smoke/build_smoke_image.sh
           echo "LOGOSCORE_IMAGE=logoscore:smoke-portable" >> $GITHUB_ENV
 
       - name: Build logoscore CLI binary (host PATH)
         # Must match the daemon commit baked into the smoke image above.
         run: |
-          nix build -L --out-link /tmp/logoscore-cli "github:logos-co/logos-logoscore-cli/5a1cf746e841e8e8a8fd48333cff55bd12c45c52#cli"
+          nix build -L --out-link /tmp/logoscore-cli "github:logos-co/logos-logoscore-cli/a9e184557aa1a29cee23837fa4af5c0a50fd1673#cli"
           echo "/tmp/logoscore-cli/bin" >> $GITHUB_PATH
 
       - uses: actions/setup-python@v5