fix(MonitorScope): don't freeze toTime on the live Monitor scope

Setting `toTime = config.toTime ?? Date.now()/1000` for the live
Monitor's `eventsGetScope` froze the upper bound at attach time.
Subsequent socket `eventsChanged` pushes triggered `events.get`
with that frozen `toTime`, so any event created after attach was
filtered out and never reached consumers — the socket fired, the
UI never updated.

Only include `toTime` when the consumer explicitly configured one;
otherwise let the Monitor default to `Number.MAX_VALUE`. The initial
paginated `events.get` keeps its `Date.now()` fallback (bounding the
backfill is correct; bounding the live listener was the bug).

Verified live in hds-webapp: external fetch from outside the app's
own MonitorScope now lands in `appService.events` within ~2.5s via
the socket push, with no page refresh.

Author: perki

ts/MonitorScope.ts

@@ -142,12 +142,15 @@ export class MonitorScope {
    */
   private async attachLiveMonitor (): Promise<void> {
     if (this.stopped) return;
-    const toTime = this.config.toTime ?? (Date.now() / 1000);
     const eventsGetScope: any = {
       fromTime: this.config.fromTime,
-      toTime,
       modifiedSince: this.maxModified,
     };
+    // Bound the live scope only if the consumer asked for one. A frozen
+    // `toTime = now` would exclude every event created after attach time —
+    // the socket's `eventsChanged` push fires, but the follow-up events.get
+    // returns nothing and the UI never updates.
+    if (this.config.toTime != null) eventsGetScope.toTime = this.config.toTime;
 
     this.monitor = new (pryv as any).Monitor(this.connection, eventsGetScope)
       .on('event', (event: Event) => {