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/custom-emoji/application/custom-emoji-sync.effects.ts

@@ -1,4 +1,3 @@
-/* eslint-disable @typescript-eslint/member-ordering */
 import { Injectable, inject } from '@angular/core';
 import { createEffect } from '@ngrx/effects';
 import { Store } from '@ngrx/store';
@@ -25,13 +24,6 @@ import { CustomEmojiService } from './custom-emoji.service';
 
 @Injectable()
 export class CustomEmojiSyncEffects {
-  private readonly customEmoji = inject(CustomEmojiService);
-  private readonly store = inject(Store);
-  private readonly webrtc = inject(RealtimeSessionFacade);
-  private readonly incomingEvents$ = merge(
-    this.webrtc.onMessageReceived,
-    this.webrtc.onSignalingMessage as Observable<ChatEvent>
-  );
 
   currentUserLoad$ = createEffect(
     () => this.store.select(selectCurrentUser).pipe(
@@ -124,4 +116,16 @@ export class CustomEmojiSyncEffects {
     ),
     { dispatch: false }
   );
+
+  private readonly customEmoji = inject(CustomEmojiService);
+
+  private readonly store = inject(Store);
+
+  private readonly webrtc = inject(RealtimeSessionFacade);
+
+  private readonly incomingEvents$ = merge(
+    this.webrtc.onMessageReceived,
+    this.webrtc.onSignalingMessage as Observable<ChatEvent>
+  );
+
 }