Don't populate channel game in subscriber

[tudddorrr]

No description provided.

[claude]

Code Review - PR #711

After reviewing this PR, the changes look good overall. The removal of the populate logic is justified since @ManyToOne relationships in MikroORM are eagerly loaded by default (unless explicitly marked with lazy: true), which is consistent with the pattern used in LeaderboardEntrySubscriber.

🟢 All Categories Clear

1. Code quality and best practices: No issues found

2. Potential bugs or issues: No issues found

3. Performance considerations: No issues found - the change actually improves performance by removing unnecessary populate operations

4. Security concerns: No issues found

5. Test coverage: No issues found - comprehensive test coverage exists in tests/subscribers/game-channel.subscriber.test.ts

---

The PR correctly simplifies the subscriber by relying on MikroORM's default eager loading behavior for the game relationship. The existing test suite should catch any issues if this assumption is incorrect.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.21%. Comparing base (6ed8919) to head (b0930b1).
⚠️ Report is 2 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #711      +/-   ##
===========================================
- Coverage    99.21%   99.21%   -0.01%     
===========================================
  Files          226      226              
  Lines        16641    16637       -4     
  Branches      1542     1540       -2     
===========================================
- Hits         16510    16506       -4     
  Misses         128      128              
  Partials         3        3              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.