Rework Raw Time Flow

[moveson]

The code that takes incoming raw time records through the matching and validation process is pretty tangled. One source of the problem is that the original consumer of this code was the Live Entry screen, which handles raw times from within Raw Time Rows (RTRs). While convenient for keeping in and out times together in the Live Entry context, RTRs get in the way when we are trying to work with individual raw time records.

All consumers of this workflow come in through Api::V1::EventGroupsController. There are three sources of this flow:

• Raw times imported and saved via the #import endpoint (as for OST Remote)
• Groups of RTRs coming from Live Entry to the #submit endpoint (when clicking the Submit button)
• Individual RTRs coming to the #enrich endpoint (throughout the Live Entry process)

The current flow looks like this:

Proposed flow for an OST Remote-style import is as follows:

1. Set parameterized split name and sortable/matchable bib numbers
2. Save to database
3. Kick off worker and send http response
   === From this point the worker takes over) ===
4. Set absolute time and lap based on entered_time and entered_lap
5. Match to existing split times
   === For unmatched raw times, continue processing ===
6. Append efforts
7. Group by effort, and for each group:
   7(a). Append new split times
   7(b). Set data status and split_time_exists
8. Save updated raw times
9. Save clean split times
10. Send notifications