Changing the object being debugged while stopped at a breakpoint has no long term effect if there was no object selected at the start of the breakpoint

The issue is that when we hit a breakpoint with no 'object to debug' set, we will set a flag bResetObjectBeingDebuggedWhenFinished to true, so after you resume execution we'll clear that flag and forget whatever you picked (or had been picked automatically). This is normally important so breakpoints work like people generally expect, but ideally if you change the dropdown while stopped at a breakpoint it would clear that flag and remember your choice.

On top of that, we should maybe have a 'keep debugging this object' option, as otherwise there's no way to elect that while stopped at a BP in this case, since there's nothing else to pick (maybe just picking even the same object should clear the bResetObjectBeingDebuggedWhenFinished flag?)

1. Have two instances of the same object in a world, put a breakpoint on the tick or wherever
2. Start the game, it will break on whichever instances ticks first
3. Change drop down to point to other instance, which should set only that one to break
4. Hit continue a few times, if this is still an issue it will break on both instances despite manually being set to the second one