fix(analytics): uniqueViewers now uses COUNT(DISTINCT viewer_id) instead of inflated groupBy

[Srejoye]

Summary

Fixes #436

The uniqueViewers field in GET /api/analytics/overview was computed using groupBy(['viewerId', 'viewerIp']), which groups on a composite key. A single authenticated viewer visiting from two different IPs produced two group rows and was counted as two unique viewers. Anonymous visitors (viewerId = null) with different IPs each added separate rows, causing severe overcounting on public profiles.

Changes

• Replace the cardView.groupBy workaround with a $queryRaw executing COUNT(DISTINCT viewer_id) — the correct SQL the code comment itself described but did not implement
• Anonymous views (viewer_id IS NULL) are explicitly excluded from the distinct count; they represent unidentifiable sessions and cannot be meaningfully deduplicated
• BigInt returned by $queryRaw is cast to Number before returning

Testing

• Seed one authenticated viewer with 5 views across 3 distinct IPs → uniqueViewers must equal 1
• Seed 3 anonymous views from 3 distinct IPs → must not inflate the count
• Seed 3 distinct authenticated viewers → uniqueViewers must equal 3
• Verified existing analytics tests pass with updated assertions

Notes

If tracking anonymous unique visitors becomes a requirement in future, a separate uniqueAnonymousVisitors field using COUNT(DISTINCT viewer_ip) can be added with explicit documentation of its limitations.

[Harxhit]

LGTM. The COUNT(DISTINCT viewer_id) query is appropriate here and keeps the aggregation in the database. Approving.

[github-actions]

Congratulations @Srejoye on getting PR #449 merged!

    Thank you for your contribution. Please mention @Harxhit in our Discord server to receive the appropriate GSSoC labels and recognition.