Please address the comments from this code review:

## Overall Comments
- The custom `RecvErr.MalformedReply` enum value is never produced by `receiveQueryReply`, but some callers (e.g. `CloudTrayMenu`) branch on it; consider either implementing malformed reply detection or removing that enum value and the associated branches to avoid dead code paths.
- Several places duplicate the same "create query receiver, iterate replies until disconnected" pattern (e.g. in `ZenohNetwork.vue`, `CloudTrayMenu.vue`, and `libs/zenoh/index.ts`); consider extracting a shared helper to centralize this logic and keep future zenoh API migrations confined to one place.

## Individual Comments

### Comment 1
<location path="core/frontend/src/libs/zenoh/index.ts" line_range="5-7" />
<code_context>
+
+// zenoh-ts 1.9 no longer exports Receiver/RecvErr; the get() channel rejects receive() on close
+// (and the query has its own timeout), so we just map that rejection to Disconnected.
+export enum RecvErr {
+  Disconnected,
+  MalformedReply,
+}
+
</code_context>
<issue_to_address>
**issue (bug_risk):** RecvErr.MalformedReply is never produced by receiveQueryReply, making callers’ MalformedReply handling unreachable.

`receiveQueryReply()` currently only returns `Reply` or `RecvErr.Disconnected` (on rejection), so there’s no path that yields `RecvErr.MalformedReply`. Callers like `CloudTrayMenu.queryFileSyncQueue` that branch on `MalformedReply` are therefore dead code. Please either wire malformed replies through to `RecvErr.MalformedReply` (e.g., via parsing error handling in `receiveQueryReply`) or remove `MalformedReply` and the unused branches to keep the enum and its usage consistent.
</issue_to_address>

### Comment 2
<location path="core/frontend/src/components/cloud/CloudTrayMenu.vue" line_range="461-462" />
<code_context>
-        let reply = await receiver.receive()
+        let reply = await receiveQueryReply(receiver)
         while (reply !== RecvErr.Disconnected) {
           if (reply === RecvErr.MalformedReply) {
             console.warn(`[CloudTrayMenu] Malformed reply while querying ${topic}.`)
           } else {
             const response = reply.result()
</code_context>
<issue_to_address>
**issue (bug_risk):** MalformedReply branch appears unreachable given current receiveQueryReply implementation.

Since `receiveQueryReply` only returns a `Reply` or `RecvErr.Disconnected`, this `MalformedReply` case is currently unreachable and malformed replies will instead be handled by the outer `catch`. Once you decide whether `receiveQueryReply` should throw on malformed input or return `RecvErr.MalformedReply`, please align this branch with that behavior or remove it.
</issue_to_address>