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/notifications/application/effects/notifications.effects.ts

@@ -1,4 +1,3 @@
-/* eslint-disable @typescript-eslint/member-ordering */
 import { Injectable, inject } from '@angular/core';
 import {
   Actions,
@@ -38,9 +37,6 @@ export function groupMessagesByRoom(messages: Message[]): Map<string, Message[]>
 
 @Injectable()
 export class NotificationsEffects {
-  private readonly actions$ = inject(Actions);
-  private readonly store = inject(Store);
-  private readonly notifications = inject(NotificationsFacade);
 
   syncRoomCatalog$ = createEffect(
     () =>
@@ -136,4 +132,11 @@ export class NotificationsEffects {
       ),
     { dispatch: false }
   );
+
+  private readonly actions$ = inject(Actions);
+
+  private readonly store = inject(Store);
+
+  private readonly notifications = inject(NotificationsFacade);
+
 }