This old logic for saving progress was giving me intermittent problems, seemed overly opaque, and still has the same # of assumptions as existing code (i.e. that what makes Exercise/VideoLog entries unique are the exercise/youtube_id and user.

So, simplified the logic (in my eyes) with no new assumptions, and the code works smoothly with no intermittent failures (including after import of KA data)