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/store/rooms/room-settings.effects.ts

@@ -1,4 +1,3 @@
-/* eslint-disable @typescript-eslint/member-ordering */
 import { Injectable, inject } from '@angular/core';
 import {
   Actions,
@@ -37,11 +36,6 @@ import { defaultChannels } from './room-channels.defaults';
  */
 @Injectable()
 export class RoomSettingsEffects {
-  private actions$ = inject(Actions);
-  private store = inject(Store);
-  private webrtc = inject(RealtimeSessionFacade);
-  private db = inject(DatabaseService);
-  private serverDirectory = inject(ServerDirectoryFacade);
 
   /** Updates room settings (host/admin-only) and broadcasts changes to all peers. */
   updateRoomSettings$ = createEffect(() =>
@@ -368,4 +362,15 @@ export class RoomSettingsEffects {
       })
     )
   );
+
+  private actions$ = inject(Actions);
+
+  private store = inject(Store);
+
+  private webrtc = inject(RealtimeSessionFacade);
+
+  private db = inject(DatabaseService);
+
+  private serverDirectory = inject(ServerDirectoryFacade);
+
 }