fix(recommended-event): Use event ID as tie breaker to match latest event

[malwilley]

Sometimes the recommended event would not match the latest event despite everything about the event being the same. I believe this is because the latest event logic uses event_id in the sort, but recommended does not:

sentry/src/sentry/models/group.py

Line 206 in a3a743c

LATEST = ["-timestamp", "-event_id"]

Adds event_id as the last item in the sort to break ties when the timestamp and everything else is the same.

[codecov]

Codecov Report

Merging #60323 (a3a743c) into master (0f418cb) will increase coverage by 0.00%.
Report is 7 commits behind head on master.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #60323   +/-   ##
=======================================
  Coverage   80.85%   80.85%           
=======================================
  Files        5183     5183           
  Lines      227698   227698           
  Branches    38316    38316           
=======================================
+ Hits       184110   184114    +4     
+ Misses      37965    37961    -4     
  Partials     5623     5623           

Files	Coverage Δ
src/sentry/models/group.py	94.49% <ø> (ø)

... and 6 files with indirect coverage changes

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ AssertionError: assert 'cccccccccccc...ccccccccccccc' == 'eeeeeeeeeeee...eeeeeeeeeeeee' pytest.runtest.protocol tests/sentry/api/endpoi... View Issue

_{Did you find this useful? React with a 👍 or 👎}