chore: enforce lint across codebase and ban "maybe" in identifiers

Remove member-ordering and complexity eslint-disable comments by reordering
class members and applying targeted fixes. Add metoyou/no-maybe-in-naming,
type-safe WebRTC e2e harness helpers, and resolve remaining lint errors so
npm run lint exits cleanly.

Co-authored-by: Cursor <cursoragent@cursor.com>

toju-app/src/app/core/services/time-sync.service.ts

@@ -1,4 +1,3 @@
-/* eslint-disable @typescript-eslint/member-ordering */
 import {
   Injectable,
   signal,
@@ -18,6 +17,10 @@ const DEFAULT_SYNC_TIMEOUT_MS = 5000;
  */
 @Injectable({ providedIn: 'root' })
 export class TimeSyncService {
+
+  /** Reactive read-only offset (milliseconds). */
+  readonly offset = computed(() => this._offset());
+
   /**
    * Internal offset signal:
    * `serverTime = Date.now() + offset`.
@@ -27,9 +30,6 @@ export class TimeSyncService {
   /** Epoch timestamp of the most recent successful sync. */
   private lastSyncTimestamp = 0;
 
-  /** Reactive read-only offset (milliseconds). */
-  readonly offset = computed(() => this._offset());
-
   /**
    * Return a server-adjusted "now" timestamp.
    *
@@ -97,4 +97,5 @@ export class TimeSyncService {
       // Sync failure is non-fatal; retain the previous offset.
     }
   }
+
 }