The contest_time may be incorrect in "runs" event feed records for long contests

[johnbrvc]

Describe the issue:
If a "runs" event occurs >= 100 hours into a contest, the contest_time will be trimmed, losing the left most hour digits.

To Reproduce:

1. Set up a contest that has been up for > 100 hours (you can use the Settings->Times pane to do this)
2. Submit a run.
3. Look at the event feed. The "runs" TestCases will all show incorrect contest_time prosperities.

Expected behavior:
The contest_time property should show the correct value.

Actual behavior:
Only the last 2 digits of the hours are included in the contest_time property.

Environment:
All

Log Info:
N/A

Screenshots:
N/A

Additional context:
The core.model.ContestTime.CONTEST_TIME_WITH_MS format constant is incorrect:
private static final String CONTEST_TIME_WITH_MS = "HH:mm:ss.SSS";
It limits hours to 2 digits.