IssueTracker

Not sure if //build/android OWNERS have bandwidth to take this, but I thought I would file this in the interest of WebView-team dev productivity.

The Generated Wrapper Scripts [1] are super cool for clank, but I think there's room for improvement when building WebView. I tried them out today, and here's some feedback:

 * /bin/system_webview_google_apk install: on N+, this should also set the webview provider
 * /bin/system_webview_google_apk argv: I'm pleasantly surprised this uses WebView's CLI file--great!
 * /bin/system_webview_google_apk launch: understandably, this fails with "APK does not support launching with URLs." But, a nice default might be to launch WebView shell instead?
 * /bin/system_webview_google_apk {logcat,ps,mem-usage}:
   - The common issue is that these don't respect WebView's browser process
   - For ps/mem-usage, it means we're missing some information
   - Logcat filtering strips browser process logs, which essentially requires using the "--verbose" flag
   - Bright side: all of these correctly handle OOP renderers on O+

Some of these issues are mitigated by switching to /bin/system_webview_shell_apk instead, but then it has new problems:

 * /bin/system_webview_shell_apk install: installs the shell, which is the right thing in this case
 * /bin/system_webview_shell_apk argv: doesn't work
 * /bin/system_webview_shell_apk launch: this works!
 * /bin/system_webview_shell_apk {logcat,ps,mem-usage}: these see the browser process, but not the renderer process

---

It'd be great to have one wrapper which has the best of both (and also sets webview provider). I'm not sure how feasible this is, but I thought I'd share my experience.

[1] https://docs.google.com/presentation/d/1TF7HRo095OcwkV963DHTAhOQ0C6ZSjaM2muYHiI0n1E/edit?usp=sharing