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/theme/infrastructure/services/theme-library-storage.service.ts

@@ -49,12 +49,13 @@ async function withTimeout<T>(operation: Promise<T>, label: string): Promise<T>
 
 @Injectable({ providedIn: 'root' })
 export class ThemeLibraryStorageService {
-  private readonly electronBridge = inject(ElectronBridgeService);
 
   get isAvailable(): boolean {
     return this.electronBridge.isAvailable;
   }
 
+  private readonly electronBridge = inject(ElectronBridgeService);
+
   async getSavedThemesPath(): Promise<string | null> {
     const electronApi = this.electronBridge.getApi();
 
@@ -218,4 +219,5 @@ export class ThemeLibraryStorageService {
       };
     }
   }
+
 }