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/direct-message/feature/find-people/find-people.component.ts

@@ -1,4 +1,3 @@
-/* eslint-disable @typescript-eslint/member-ordering */
 import {
   Component,
   computed,
@@ -16,7 +15,7 @@ import {
   lucideUsers
 } from '@ng-icons/lucide';
 
-import { AppI18nService, APP_TRANSLATE_IMPORTS } from '../../../../core/i18n';
+import { APP_TRANSLATE_IMPORTS } from '../../../../core/i18n';
 import { AutoFocusDirective, SelectOnFocusDirective } from '../../../../shared/directives';
 import { UserSearchListComponent } from '../user-search-list/user-search-list.component';
 import { selectAllUsers } from '../../../../store/users/users.selectors';
@@ -47,10 +46,7 @@ import { selectSavedRooms } from '../../../../store/rooms/rooms.selectors';
   }
 })
 export class FindPeopleComponent {
-  private store = inject(Store);
   searchQuery = signal('');
-  private users = this.store.selectSignal(selectAllUsers);
-  private savedRooms = this.store.selectSignal(selectSavedRooms);
 
   /** True when the account has any people to surface (known users or server members). */
   hasDiscoverablePeople = computed(() => {
@@ -61,7 +57,14 @@ export class FindPeopleComponent {
     return this.savedRooms().some((room) => (room.members?.length ?? 0) > 0);
   });
 
+  private store = inject(Store);
+
+  private users = this.store.selectSignal(selectAllUsers);
+
+  private savedRooms = this.store.selectSignal(selectSavedRooms);
+
   onSearchChange(query: string): void {
     this.searchQuery.set(query);
   }
+
 }