[TIMOB-11173] Android: Debugger: breakpoint at global unassigned variable declaration hits next statement instead

Breakpoints at global unassigned variable declarations are skipped and hit at next statement instead. However, unassigned variable declarations in anonymous functions are correctly hit. For example:

var deadVar1; // breakpoint

Ti.API.info('Global Variables Defined!');

(function(){
	var deadVar2; // breakpoint
	
	Ti.API.info('Anonymous Function Called!');
})();

alert('App Exited!');

Running this code in debug mode will result in the first breakpoint being hit at the next statement (e.g., 'var deadVar1' stops at 'Ti.API.info('Global Variables Defined!')'). Steps to Reproduce: 1. Run code in debug (manually insert breakpoints as per code comments):

var deadVar1; // breakpoint

Ti.API.info('Global Variables Defined!');

(function(){
	var deadVar2; // breakpoint
	
	Ti.API.info('Anonymous Function Called!');
})();

alert('App Exited!');

Actual Result: App skips the first breakpoint, but stops at the next statement. Pressing 'Resume' will correctly hit the unassigned variable in the anonymous function. Expected Result: The first breakpoint should be hit and pressing 'Resume' should hit the next breakpoint. Here is the expected console log for the sample code:

[INFO] Global Variables Defined!
[INFO] Anonymous Function Called!