tree dc6daacf40273cef8dc782f582ce6ccd73436edc
parent 92160d6e9fb1caa1142599ee252f53b796298be5
author Joshua Trask <joshtrask@google.com> 1670880376 -0500
committer Joshua Trask <joshtrask@google.com> 1671120191 +0000

Extract remainining ChooserActivity logging

This especially covers other kinds of logging in ChooserActivity that
hadn't previously been a responsibility of ChooserActivityLogger (e.g.
because they instead went directly through MetricsLogger).

There's a few reasons to make these changes, in rough priority order:

 1. Tests can make assertions about the high-level logging methods we
    expect to call; the implementation of those methods (in terms of
    low-level event streams) is unit-tested for the logger itself.

 2. We can encapsulate all the types of loggers (UiEventLogger,
    MetricsLogger, etc.) in a single object, which is easier to inject
    as a dependency as we continue decomposing ChooserActivity
    responsibilities into other components.

 3. High-level logger APIs reduce the clutter that clients previously
    spent building up the low-level event data that's now abstracted
    away.

Test: atest IntentResolverUnitTests
Bug: 202167050
Change-Id: Ib3197bca12ec5ea3c925946c0f6d37a6be19d8fa