chore: bump the module loader for the host logging fix (#173)

logos-module-loader-qt#5 makes logos_host install its own Qt message
handler, so a module's diagnostics reach the daemon that spawned it
instead of being diverted to journald by Qt's default backend.

liblogos is the carrier: nothing downstream sees that fix until this pin
moves. Measured end to end on Linux with the two halves in place (this
loader plus logos-logoscore-cli#83, which fixes a -v that never reached
the daemon and raises spdlog's level so the forwarded records survive):
module lines in a session log went from 1 to 46, and the 59 lines per
install that were escaping to journald went to 0.

Single-input bump; nothing else in the lock moved. `nix flake check`
green.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

flake.lock

@@ -74,11 +74,11 @@
         ]
       },
       "locked": {
-        "lastModified": 1784686952,
-        "narHash": "sha256-0QVyGF6cpDz8RLozz1qypS7a/k0w6yBs9zGlkZMxZe4=",
+        "lastModified": 1785971700,
+        "narHash": "sha256-Nj4wv/PyvY9Kyuv5rsop/fQ5utm1X52zWiXPeDXSJEA=",
         "owner": "logos-co",
         "repo": "logos-module-loader-qt",
-        "rev": "bc46dbfc5e2fbbe259fbd30982bf563a772b918b",
+        "rev": "811d83407822091817719d8e46de26e548e23b19",
         "type": "github"
       },
       "original": {