Fix request audit log ordering

[shubhamsinnh]

Summary

• Add a deterministic secondary sort for request audit logs when multiple entries share the same timestamp.
• Stop rendering generated sample rows in audit log tables while real log data is loading.

Why

Request audit log entries store timestamps at second-level precision. Under high activity, many entries can share the same timestamp. The request log query sorted only by timestamp, so separate executions for the GUI and CSV export could return same-timestamp rows in different orders. That can make row-by-row comparisons look like the GUI mixed data even when each individual row is valid.

Request logs now sort by timestamp descending and then id descending, matching the deterministic ordering pattern already used by action, access, and connection audit log queries.

Audit log pages also now render only real API data instead of generated placeholder rows while loading.

Fixes #3458.

Validation

• git diff --check HEAD~1 HEAD
• npx prettier --check server/routers/auditLogs/queryRequestAuditLog.ts 'src/app/[orgId]/settings/logs/access/page.tsx' 'src/app/[orgId]/settings/logs/action/page.tsx' 'src/app/[orgId]/settings/logs/connection/page.tsx' 'src/app/[orgId]/settings/logs/request/page.tsx'
• npx tsc --noEmit --pretty false
• Inserted a local burst of 50 same-timestamp request audit rows to verify the high-activity shape, then removed the synthetic rows afterward.