Lockloss states 103-~200 sometimes incorrectly labeled

LHO has recently been having a string of TURN_ON_BS_STAGE_2 locklosses, and in searching for some to test on I realized that I wasn't able to find any locklosses from that state or nearby states happening later than December last year. I used ndscope to look at the ISC_LOCK state for a lockloss that was marked in Jenne's re-acquisition survey (by me) as a TURN_ON_BS_STAGE_2 loss, and it turns out that ISC_LOCK was bumped back to ACQUIRE_DRMI_1F for a fraction of a second before losing lock (see attached).

This would normally register as 2 locklosses, but the integer precision of the lockloss ID system writes over the first (correct) lockloss. I believe we have a lot of recent locklosses that have been miscategorized as ACQUIRE_DRMI_1F locklosses, we should tweak our state-finding method and ideally re-run on previous locklosses.