[Bundle workflow] Breakpoint in linked source not hit in VSCode on lightweight app initial load

Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):

• CLI: rc
• Cross-platform modules: rc
• Android Runtime: rc

Describe the bug
Breakpoint in linked tns-core-modules source is not hit in VSCode on initial app start when using a very thin (lightweight) NativeScript app (e.g. created from blank template) even when stopOnEntry is set to true. After initial load debugging works as expected. A workaround proposed by @DimitarTachev is to place a debugger; statement in the beginning of the file-to-debug.

To Reproduce

1. git clone git@github.com:NativeScript/NativeScript.git
2. cd NativeScript
3. tns create bottom-nav-test --template tns-template-blank-ts
4. cd bottom-nav-test
5. tns migrate
6. Open NativeScript folder in VSCode
7. Replace the contents of bottom-nav-test/app-root.xml with:

<BottomNavigation>
    <TabStrip>
        <TabStripItem title="First"></TabStripItem>
        <TabStripItem title="Second"></TabStripItem>
    </TabStrip>

    <TabContentItem>
        <GridLayout>
            <Label text="First View" />
        </GridLayout>
    </TabContentItem>

        <TabContentItem>
        <GridLayout>
            <Label text="Second View" />
        </GridLayout>
    </TabContentItem>
</BottomNavigation>

8. Place a breakpoint in the OnLoaded() method in tns-core-modules/ui/bottom-navigation/bottom-navigation.android.ts
9. Configure NativeScript debugging and add the following debug configuration in launch.json:

        {
            "name": "bottom-nav | Launch on Android",
            "type": "nativescript",
            "request": "launch",
            "platform": "android",
            "appRoot": "${workspaceRoot}/bottom-nav-test",
            "sourceMaps": true,
            "stopOnEntry": true,
            "watch": true
        },

10. Try to debug using the newly added configuration
11. Breakpoint in OnLoaded() is not hit

Expected behavior
Breakpoints should work on initial app start as well

Reproduce the lightweight Android app using the listed NativeScript commands, then start with tns-core-modules/ui/bottom-navigation/bottom-navigation.android.ts and the stopOnEntry configuration in launch.json. Trace the initial startup and source-map debugging flow to determine why OnLoaded() is skipped, using the debugger workaround as a comparison. Done means the breakpoint is hit during initial app load without adding debugger;.