Move Google passwords import pixels to the import web flow

[catalinradoiu]

Task/Issue URL: https://app.asana.com/1/137249556945/project/1202552961248957/task/1218056082137357?focus=true
Tech Design URL (if applicable): https://app.asana.com/1/137249556945/project/481882893211075/task/1217143698674642
API Proposals URL(s) (if applicable): None

Description

Moves the Google Password Manager import result pixels from the consumers of the import web flow into the web flow itself, so that new consumers (like the onboarding passwords import step) don't need their own import pixel logic.

• The user-cancelled, CSV-parsing-error and WebView-crash pixels now fire from ImportGooglePasswordsWebFlowViewModel, which receives the launch source via assisted injection (activity params → fragment args → assisted factory).
• The import success pixel now fires from a new app-scoped ImportPasswordsResultPixelObserver that observes CredentialImporter.getImportStatus() from process start, with the launch source carried in ImportResult.Finished. This keeps the pixel firing even though the import outlives the screen that started it.
• ImportFromGooglePasswordsDialog(ViewModel) no longer fires the result pixels; the pre-import prompt pixels stay there since that prompt is the dialog's own UI.
• Registers the existing import pixels (plus the new onboarding source value) in PixelDefinitions/pixels/definitions/autofill.json5.

Steps to test this PR

Import from password management

• Settings → Passwords → import passwords from Google → complete the web flow; verify autofill_import_google_passwords_result_success fires once with bucketed saved_credentials/skipped_credentials and the correct source
• Start the web flow and cancel it; verify autofill_import_google_passwords_result_user_cancelled fires once with the web flow stage and source

Import from onboarding

• Apply the following patch

NewUserOnboardingPlanProvider.kt — force-enable password import steps

diff --git a/app/src/main/java/com/duckduckgo/app/onboarding/orchestrator/NewUserOnboardingPlanProvider.kt b/app/src/main/java/com/duckduckgo/app/onboarding/orchestrator/NewUserOnboardingPlanProvider.kt
--- a/app/src/main/java/com/duckduckgo/app/onboarding/orchestrator/NewUserOnboardingPlanProvider.kt
+++ b/app/src/main/java/com/duckduckgo/app/onboarding/orchestrator/NewUserOnboardingPlanProvider.kt
@@ -202,7 +202,7 @@
                     add(widgetPromptStep(ctx))
                     add(addWidgetStep(ctx))
                 }
-                if (showPasswordImport) {
+                if (true) {
                     add(passwordImportStep(ctx))
                     add(passwordImportLaunchStep(ctx))
                     add(passwordImportCompleteStep(ctx))

• Fresh install with the onboarding password import step enabled → run the import from onboarding; verify the same result pixels fire with source=onboarding

UI changes

Before	After
No UI changes	No UI changes

---

Note

Medium Risk
Changes where import outcome pixels fire and extends the credential import API with launch source; risk is mainly duplicate or missed telemetry if replay/collection timing is wrong, not credential handling logic.

Overview
Centralizes Google Password Manager import telemetry so new entry points (e.g. onboarding) do not duplicate pixel logic.

Pixel definitions in autofill.json5 now document the pre-import prompt, success (bucketed counts), user-cancelled (stage + source), CSV parse failure, and WebView crash events, including an onboarding launch source.

Web flow threads AutofillImportLaunchSource from activity params → fragment args → assisted ImportGooglePasswordsWebFlowViewModel, which fires cancel, parse error, and WebView crash pixels. CredentialImporter takes source and includes it on ImportResult.Finished; a new app-scoped ImportPasswordsResultPixelObserver emits the success pixel after bulk insert completes (even if the starting screen is gone). ImportFromGooglePasswordsDialog no longer fires result pixels (pre-import prompt pixels stay). ImportPasswordsPixelSender moves to AppScope.

Onboarding only renames onContentBound → onBeforeContentBound in the config-driven content controller hook.

^{Reviewed by Cursor Bugbot for commit 72203d3. Bugbot is set up for automated code reviews on this repo. Configure here.}

[catalinradoiu]

• Move Google passwords import pixels to the import web flow #9674 👈 (View in Graphite)
• Wire the onboarding password import step to the Google import flow #9624 : 1 other dependent PR (#9686 )
• Add the password import step UI to the onboarding #9623
• develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Privacy Review task: https://app.asana.com/0/69071770703008/1218020222494663

[catalinradoiu]

Will update this #9624 (comment) as part of this PR.

[catalinradoiu]

Follow-up after #9624 (comment)