(Task 3) Feature: Race Status field

[Cuttsy27]

Changes

• added Status enum to Race message
• added addStatusToRace/s methods to race repo
• added timestamp utility functions
• added tests for all

Summary

Races should have a Status field which is derived from their advertised_start_time property. A race in the past has status "CLOSED" and a race in the future has status "OPEN". As the Status is derived from the advertised_start_time, there are no DB changes to be made. When races are retrieved from the database, we iterate over the result and update the Status property of each race by comparing the current time to the advertised_start_time.

Example

curl -X "POST" "http://localhost:8000/v1/list-races" \
     -H 'Content-Type: application/json'

{
    "races":[
        {
            "id":"1",
            "meetingId":"5",
            "name":"North Dakota foes",
            "number":"2",
            "visible":false,
            "advertisedStartTime":"2021-03-03T01:30:57Z",
            "status":"CLOSED"
        }
    ]
}

Tests

• We added tests for the new addStatusToRace and addStatusToRaces methods with 100% coverage
• We added tests for each of the new utility functions IsProtoTimestampInPast, GetCurrentProtoTimestamp, GetProtoTimestamp, with 100% coverage
• We tested the racing service to ensure it correctly handles races with the new Status property.