This reverts commit 6fb061ce5efc1a3fb11dace06b826382e0b56736.
These didn't work out in practice. The file lists were always empty, I
think it might be a difference in permissions for release builds vs the
debug builds that I was testing with.
The package installer name was useful, but I realized there's Sentry tag for that which is even more useful.
When we have an existing `engineSession` we use an optimized route to
load the url without needing to dispatch the load action. This is still
a valid performance improvement to make page loads faster.
However, in this code path we do not end up update the url in the state
until we get back a response from the Engine. This gives a perceived
performance loss of slow browsing. Updating the url gives UI components
an immediate update which reflects a change that would have been entered
by the user.
It was considered if we should do this in a middleware, but since this
is an optimized route, we should not wait for the middleware to process
the action before we perform the state update.
This commit:
* Sends the new `awesomebar.{engagement, abandonment}` events when the
user finishes interacting with the awesomebar. These events match
iOS's events of the same name, and Desktop's
`urlbar.{engagement, abandonment}` events.
* Removes the `engagement_abandoned` extra key for the
`awesomebar.{sponsored, non_sponsored}_suggestion_impressed` events,
since they're specific to AMP and Wikipedia suggestions, and are
subsumed by the new events.
This is the first step toward unifying our awesomebar search telemetry
on all our platforms.
This patch refactors a few things for fetching supported languages:
* `TranslateExpectedAction` is decoupled from fetching languages
* Now use `OperationRequestedAction` w/ `FETCH_SUPPORTED_LANGUAGES`
* Refactors the Fenix fragment to send `OperationRequestedAction` as a
placeholder for data initialization
* `TranslateSetLanguagesAction` is now `SetSupportedLanguagesAction`