fix: add deterministic tiebreaker to event list ordering

[decentraland-bot]

Summary

• Adds e.id ASC as a secondary sort key to the getEvents query, so events with the same next_start_at always return in a stable, reproducible order.
• Fixes Fix non-deterministic event ordering in Genesis Plaza map panel unity-explorer#9529 — the Events tab in the Genesis Plaza map panel was displaying events in a non-deterministic order that shuffled on every open.
• Addresses the review feedback to fix this at the backend level so all consumers benefit.

Why

PostgreSQL does not guarantee row order when the ORDER BY column has ties. Multiple events at the same location often share the same next_start_at, producing a random order on every query.

Test plan

• All 199 existing unit tests pass
• TypeScript compiles cleanly
• Verify on staging: open the Genesis Plaza Events tab multiple times and confirm the order is stable

🤖 Generated with Claude Code

[decentraland-bot]

Review verdict: PASS (no blocking findings). GitHub does not allow this account to approve a PR it authored, so I am leaving this as a review comment.

No P0/P1 issues found.

Findings:

• Public API impact: backward-compatible. This only defines previously unspecified tie ordering for existing event list responses; request/response shape, filters, pagination parameters, and primary chronological/search-rank ordering remain unchanged.
• Security: No security issues found. The added SQL fragment is static, and the existing raw orderBy / orderDirection values remain whitelist-derived.
• Test coverage: A focused regression test for identical next_start_at values would be useful, but I do not consider it blocking for this one-line deterministic tie-breaker.
• Git conventions: PR title and branch follow the semantic fix: convention.

CI status at review time: Prettier and lint-and-test are passing; build-image and integration-tests are still pending.

---

Reviewed by Jarvis 🤖 · Requested by Alejandro Jimenez (<@U0ADNDHL1T7>) via Slack