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/attachment/infrastructure/services/electron-attachment-file-store.ts

@@ -6,11 +6,12 @@ import type { AttachmentFileStore } from './attachment-file-store';
 @Injectable({ providedIn: 'root' })
 export class ElectronAttachmentFileStore implements AttachmentFileStore {
   readonly maxPersistableBytes = Number.POSITIVE_INFINITY;
-  readonly supportsStreamingToDisk = true;
-  readonly supportsChunkedReads = true;
-  readonly providesInlineObjectUrl = false;
 
-  private readonly electronBridge = inject(ElectronBridgeService);
+  readonly supportsStreamingToDisk = true;
+
+  readonly supportsChunkedReads = true;
+
+  readonly providesInlineObjectUrl = false;
 
   get isAvailable(): boolean {
     const electronApi = this.electronBridge.getApi();
@@ -18,6 +19,8 @@ export class ElectronAttachmentFileStore implements AttachmentFileStore {
     return !!electronApi?.appendFile && !!electronApi.writeFile && !!electronApi.getAppDataPath;
   }
 
+  private readonly electronBridge = inject(ElectronBridgeService);
+
   async getAppDataPath(): Promise<string | null> {
     const electronApi = this.electronBridge.getApi();
 
@@ -169,4 +172,5 @@ export class ElectronAttachmentFileStore implements AttachmentFileStore {
       return null;
     }
   }
+
 }