Breakpoints in code run later in the frame are still hit after hitting stop at a previous breakpoint when debugging BPs

We can't prevent code after the stop from being run until the end of the frame, but we should be able to prevent it from actually stopping at those breakpoints if a stop was requested previously.

It's unclear if this is desired 100% of the time or not, so we should probably pick a best choice as default and let it be an option, but I'm open to debate on that.