[TIMOB-26099] Android: Modified "appc run" to launch app with same intent as Android OS when tapping app

[jquick-axway]

JIRA:

• https://jira.appcelerator.org/browse/TIMOB-26099
• https://jira.appcelerator.org/browse/TIMOB-25867

Summary:

• Modified appc run to use same intent settings the Android OS uses when tapping on an app.

• We were missing intent action "MAIN and category "LAUNCHER".

• Fixes issue where pressing "Home" button after appc run app launch and then tapping on the app onscreen would not resume the app. Would launch a new splash-screen, but not run the app.
• Fixed regression caused by TIMOB-25867 where "Restart Required" dialog would be displayed infinitely on app launch on Pixel XL.

Test:
Run the below test on a Pixel XL, Android 4.1 device, and in the Android emulator.

1. Build and run the below code via Appcelerator Studio or via appc run.
2. Verify that the app's splash screen is not launched twice. (This ensures that TIMOB-25867 is still fixed.)
3. Once launched, press the "Home" button to suspend the app. (Do NOT press "Back".)
4. Go to the main app list screen. (Do NOT press the "Square" button.)
5. Tap on the app from the list screen.
6. Verify that the app resumes and it is not stuck at the splash screen.

var window = Ti.UI.createWindow();
window.add(Ti.UI.createLabel({ text: 'Test' }));
window.open();

[ypbnv]

LGTM

[jquick-axway]

@ypbnv, for your info, the regression I mentioned only happened to me on 1st generation Pixel phones. I couldn't reproduce the issue on other devices. It wasn't an issue on a Pixel 2 either. Strange... but the intent generated on the Pixel was definitely different than the rest and I decided it was better to provide an explicit intent instead... which also solved the other ticket's issue. Thanks.

[cb1kenobi]

Tested it and while I couldn't reproduce the issue, this PR doesn't appear to break anything. APPROVED

[jquick-axway]

I've tested this change on the following:

• Pixel XL (Android 8.0)
• Galaxy Nexus (Android 4.1)
• Amazon Fire HD 8 Tablet
• Android 6.0 Emulator
• Android 4.4 Emulator

[ypbnv]

@jquick-axway I have a Pixel (first gen) at hand and I was not able to reproduce the described regression. But I won't be surprised if it happens on XL only. Another thing I noticed is that when you start an application without the -n option the intent is automatically given the category and action that match the launch from clicking the icon (the same we add with this PR). If I add the -n option the intent does not have them. I tried it on real devices with APIs 23/24/26. We are ensuring we get the same result every time so that would cover exceptions of this behavior.

[jquick-axway]

@ypbnv, thanks for testing it out. Weird that my Pixel XL is the only device so far that doesn't follow the rules. Well, Android is the wild-west of operating systems. Unfortunately, these things happen.

The "real" solution is to refactor our intent handling on app startup/resume. This is the source of our problems. I plan on doing so for Titanium 8.0.
https://jira.appcelerator.org/browse/TIMOB-26075