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/infrastructure/realtime/streams/peer-media-facade.ts

@@ -13,9 +13,6 @@ interface PeerMediaFacadeDependencies {
 }
 
 export class PeerMediaFacade {
-  constructor(
-    private readonly dependencies: PeerMediaFacadeDependencies
-  ) {}
 
   get onMessageReceived(): Observable<ChatEvent> {
     return this.dependencies.peerManager.messageReceived$.asObservable();
@@ -37,6 +34,10 @@ export class PeerMediaFacade {
     return this.dependencies.mediaManager.voiceConnected$.asObservable();
   }
 
+  constructor(
+    private readonly dependencies: PeerMediaFacadeDependencies
+  ) {}
+
   getActivePeers(): Map<string, PeerData> {
     return this.dependencies.peerManager.activePeerConnections;
   }
@@ -134,4 +135,5 @@ export class PeerMediaFacade {
     this.dependencies.mediaManager.destroy();
     this.dependencies.screenShareManager.destroy();
   }
+
 }