Add end-to-end tests for TLS RPT report ingestion and WebSocket event handling

- Implemented tests for ingesting TLS RPT reports from emails and ensuring they are stored correctly in the database.
- Added tests to verify that the same report can be ingested multiple times without duplication.
- Created tests for backfilling reports that were previously delivered to the inbox.
- Developed WebSocket event handling tests to ensure events are correctly routed to subscribers based on mailbox ownership.
- Included tests for the mail API to validate session handling, mailbox isolation, and error mapping.
- Ensured that the API rejects unauthorized requests and handles malformed JSON gracefully.

services/auth/src/repository.ts

@@ -686,7 +686,12 @@ export async function createMailbox(scope: AdminScope, input: CreateMailboxInput
     `INSERT INTO folders (mailbox_id, name, special_use)
      SELECT $1, f.name, f.special_use
        FROM (VALUES ('INBOX','inbox'), ('Sent','sent'), ('Drafts','drafts'),
-                    ('Trash','trash'), ('Junk','junk'), ('Archive','archive')) AS f(name, special_use)`,
+                    ('Trash','trash'), ('Junk','junk'), ('Archive','archive'),
+                    -- Where delivered DMARC and TLS-RPT reports are filed.
+                    -- IMAP has no special-use role for these, so it is matched
+                    -- by name. Without the folder the delivery path falls back
+                    -- to INBOX, which is the noise this is here to remove.
+                    ('Reports', NULL)) AS f(name, special_use)`,
     [created!.id],
   );