GeezerVison

PR Checklist

• The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/tools/notes/CONTRIBUTING.md#commit-messages.
• There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
• You have signed the CLA.
• All existing tests are passing: https://github.com/NativeScript/NativeScript/blob/master/tools/notes/DevelopmentWorkflow.md#running-unit-tests-application.
• Tests for the changes are included - https://github.com/NativeScript/NativeScript/blob/master/tools/notes/WritingUnitTests.md.

What is the current behavior?

The legacy launch event fires only for the first window of the process, because _launchBridgeConsumed is set once and never reset. On Android 10 and 11, Back on the root activity finishes it and exit fires, but the process stays alive. When the user reopens the app, the new activity doesn't fire launch again. @nativescript/angular bootstraps only in its launch handler and tears the app down on exit, so the app stays unstyled and unresponsive until the process is killed. This worked in 9.0.x, where every new activity without saved state fired launch.

What is the new behavior?

ApplicationCommon re-arms the launch bridge when exit fires, so the first window after an exit fires launch again. Windows opened while the app is running still don't fire it, so multi-window behaviour is unchanged.

Added a unit test in window-content-resolver.spec.ts that fails without the fix. Also verified on a physical Android 11 device with an Angular app built against this branch: leaving with Back and reopening now bootstraps the app again.

Fixes #11572.