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/domains/chat/feature/chat-image-proxy-fallback.directive.ts

@@ -15,11 +15,20 @@ import type { RoomSignalSourceInput } from '../../server-directory';
   standalone: true
 })
 export class ChatImageProxyFallbackDirective {
+
+  @HostBinding('src')
+  get src(): string {
+    return this.renderedSource();
+  }
+
   readonly sourceUrl = input('', { alias: 'appChatImageProxyFallback' });
+
   readonly signalSource = input<RoomSignalSourceInput | null>(null);
 
   private readonly klipy = inject(KlipyService);
+
   private readonly renderedSource = signal('');
+
   private hasAppliedProxyFallback = false;
 
   constructor() {
@@ -29,11 +38,6 @@ export class ChatImageProxyFallbackDirective {
     });
   }
 
-  @HostBinding('src')
-  get src(): string {
-    return this.renderedSource();
-  }
-
   @HostListener('error')
   handleError(): void {
     if (this.hasAppliedProxyFallback) {
@@ -49,4 +53,5 @@ export class ChatImageProxyFallbackDirective {
     this.hasAppliedProxyFallback = true;
     this.renderedSource.set(proxyUrl);
   }
+
 }