I don't understand how this works before, but this fixes the recent test regressions on Windows in TestConsecutiveBreakpoints.py.
LLDB wasn't stopping when single-stepping onto a breakpoint. (Note that process continue from one breakpoint starts with a single-step, so you don't have to be explicitly single-stepping to run into this problem.)
The solution is to check if the single step lands on a breakpoint, and, if it does, to treat that like a breakpoint hint. Note there's a subtle difference in the PC (program counter) compared to actually hitting a breakpoint.
This fixes TestConsecutiveBreakpoints.py on Windows, and no other tests regress. Ran clang-format.