End times inconsistent on event feed for "judgements"

[johnbrvc]

Describe the issue:
For "judgements" type events, the data object contains several time properties: start_time, start_contest_time, end_time, end_contest_time. It seems the end_time and the end_contest_time can be less than the corresponding start_time and start_contest_time:

{"type":"judgements", "id":"pc2-1975", "op":"create", "data": {"id":"Run--4136172624303351484","submission_id":"6",
    "start_time":"2023-10-29T11:20:49.029-04","start_contest_time":"00:05:49.094","judgement_type_id":"AC",
    "end_time":"2023-10-29T11:20:00-04","end_contest_time":"00:05:00.000"}}

To Reproduce:

1. Start a completed contest (one with submissions and judgments)
2. Start an event feeder server
3. Using curl, read the event feed to a file: curl -k https://admin:admin@localhost:50443/contest/event-feed >ef.json
4. Edit the produced ef.json and search for "judgements" events.
5. Note the end times. (see example above) They are less than the corresponding start times.

Expected behavior:
The end times should be greater than or equal to the corresponding start times.

Actual behavior:
The end times are less than the start times. (rounded down to the previous minute).

Environment:
All.

Log Info:

Screenshots:

Additional context:
It looks like PC2 uses the floor of the contest minute as the end time for judgments, it probably shouldn't do this.

[johnbrvc]

Duplicate of #712