fix(audit): enforce tenant scoping for audit log queries

[kryputh]

Prevent cross-tenant leakage by enforcing tenant scoping in audit log repositories and routes.

Key changes:

• Updated AuditLogService to require tenantId for all logging and retrieval operations.
• Implemented tenant-aware filtering in PostgresAuditLogsRepository and InMemoryAuditLogsRepository.
• Refactored all administrative services (Webhooks, Replay, Policy, Members, Impersonation) to pass the authenticated user's tenantId to the audit trail.
• Enforced strict scoping in routes by passing the tenantId from the authenticated request context.
• Fixed potential ReferenceError in admin route catch blocks by ensuring the next parameter is correctly defined and utilized.
• Verified isolation logic with updated unit tests.

Scoping Policy:

• Standard Admin: Restricted strictly to their own tenantId.
• Super Admin: Can view all logs or filter by specific tenant if allowSuperScope is explicitly enabled.

Closes #228

[drips-wave]

@kryputh Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits