[dPWA] Refactoring launches to always be async.

Context:
Reading information from the WebAppProvider system is often inherently
racy (given all of our async data sources). Putting operations behind
commands guarantees the the data read is not going to change across
async calls (and that you aren't reading it in the middle of an
operation like 'install', 'uninstall', etc).

This project protects 'launch' to make sure it doesn't happen during
an 'uncommitted read' state.

This change was created by using 'git cl split', and is the first part
in making dPWA launches async. The app service is designed to have
launches be async (and in lacros they will ALWAYS be async), but
currently they are "mostly" synchronous. This means that there are a
variety of tests (and even one instance of production code - the
intent launcher) which assumes this. This patch fixes all of those
cases.

Specifically patches split here:
* Add browser or navigation waiters to wait until launches complete in
  tests.
* Modifies the method signatures required for making launches async for
  making launches async (but just calls the callback synchronously for
  now.
* Fixes a future bug for Lacros where the intent navigation closes the
  window before launching the app, causing the browser/profile to start
  shutting down. Keep-alives were added to ensure this does not happen.

There is no functional change in this patch.
If you want to see a patch with all test changes & functionality
changes, see:
https://chromium-review.googlesource.com/c/chromium/src/+/3929017

$description

This CL was uploaded by git cl split.

R=tobyhuang@chromium.org

Bug: b/242059352, 1377102
Change-Id: Ifffb6083d65c69de119475c7720779e579581481
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3969023
Reviewed-by: Toby Huang <tobyhuang@chromium.org>
Auto-Submit: Daniel Murphy <dmurph@chromium.org>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1062966}
2 files changed
tree: 282c4266d0cb5cc2d1f5c696499d745448b821f2
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.