Enable native input for internal builds

Flip the nativeInputField feature flag default to INTERNAL and
remove the now-redundant user toggle from AI Features settings.
Widget visibility is driven by the feature flag, with the existing
observer API in DuckChat backed by the cached flag value so all
consumers (omnibar, NTP, system search, native and contextual
input managers, JS helper) pick it up unchanged.

Adjust the Maestro flows that run on the internal binary so the
NTP omnibar — which now starts behind the native input widget —
is dismissable before the menu / address bar is needed:

- Add a shared ../shared/dismiss_native_input.yaml helper that
  taps the widget's back arrow (inputModeUnifiedBack) when visible.
- Have shared/browser_screen/click_on_menu_button.yaml dismiss the
  widget first, so any flow tapping the menu through the helper
  (custom tabs, ADS, sync) keeps working.
- Route privacy_tests_internal and duckplayer_settings through
  the same helper instead of tapping the menu directly.
- Dismiss the widget before tapping omnibarTextInput in the
  duckplayer direct/common flows and in sync's add_bookmarks step.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: 2 people

.maestro/duckplayer/common/input_search.yaml

@@ -1,6 +1,7 @@
 appId: com.duckduckgo.mobile.android
 ---
 # Select a YouTube video from SERP
+- runFlow: ../../shared/dismiss_native_input.yaml
 - tapOn:
     id: "omnibarTextInput"
 - inputText: "https://duckduckgo.com/?q=DuckDuckGo%20vs%20Google%3A%205%20Reasons%20You%20Should%20Switch%20video%20site%3Ayoutube.com&ko=-1&ia=web"

.maestro/duckplayer/common/load_youtube_video.yaml

@@ -3,6 +3,7 @@ appId: com.duckduckgo.mobile.android
 androidWebViewHierarchy: devtools
 ---
 # Navigate to a YouTube video
+- runFlow: ../../shared/dismiss_native_input.yaml
 - tapOn:
     id: "omnibarTextInput"
 - inputText: "https://m.youtube.com/@duckduckgo2597/search?query=DuckDuckGo%20vs%20Google%3A%205%20Reasons%20You%20Should%20Switch"

.maestro/duckplayer/direct_duckplayer.yaml

@@ -11,6 +11,7 @@ tags:
 
       - runFlow: ../shared/skip_all_onboarding.yaml
 
+      - runFlow: ../shared/dismiss_native_input.yaml
       - tapOn:
           id: "omnibarTextInput"
       - inputText: "duck://player/3ml7yeKBUhc"

.maestro/duckplayer/direct_duckplayer_playback.yaml

@@ -11,6 +11,7 @@ tags:
 
       - runFlow: ../shared/skip_all_onboarding.yaml
 
+      - runFlow: ../shared/dismiss_native_input.yaml
       - tapOn:
           id: "omnibarTextInput"
       - inputText: "duck://player/3ml7yeKBUhc"

.maestro/duckplayer/direct_duckplayer_youtube.yaml

@@ -12,6 +12,7 @@ tags:
 
       - runFlow: ../shared/skip_all_onboarding.yaml
 
+      - runFlow: ../shared/dismiss_native_input.yaml
       - tapOn:
           id: "omnibarTextInput"
       - inputText: "duck://player/3ml7yeKBUhc"

.maestro/duckplayer/duckplayer_settings.yaml

@@ -11,8 +11,7 @@ tags:
 
       - runFlow: ../shared/skip_all_onboarding.yaml
 
-      - tapOn:
-          id: "com.duckduckgo.mobile.android:id/browserMenuImageView"
+      - runFlow: ../shared/browser_screen/click_on_menu_button.yaml
 
       - scrollUntilVisible:
           element:

.maestro/privacy_tests_internal/1_-_Api_manipulation.yaml

@@ -8,8 +8,7 @@ tags:
       - launchApp:
           clearState: true
       - runFlow: ../shared/skip_all_onboarding.yaml
-      - tapOn:
-          id: "com.duckduckgo.mobile.android:id/browserMenu"
+      - runFlow: ../shared/browser_screen/click_on_menu_button.yaml
       - tapOn:
           id: "com.duckduckgo.mobile.android:id/settingsMenuItem"
       - scrollUntilVisible:
@@ -43,6 +42,7 @@ tags:
       - pressKey: Back
       - pressKey: Back
       - pressKey: Back
+      - runFlow: ../shared/dismiss_native_input.yaml
       - assertVisible:
           id: "com.duckduckgo.mobile.android:id/omnibarTextInput"
       - inputText: "https://privacy-test-pages.site/content-scope-scripts/infra/pages/conditional-matching-experiments.html?automation=1"

.maestro/shared/browser_screen/click_on_menu_button.yaml

@@ -1,5 +1,10 @@
 appId: com.duckduckgo.mobile.android
 ---
+# With the native input field enabled, the NTP shows the native input widget
+# over the omnibar (no browser menu visible). Dismiss it first so the menu
+# is exposed before we try to use it.
+- runFlow: ../dismiss_native_input.yaml
+
 - runFlow:
     when:
         notVisible:

.maestro/shared/dismiss_native_input.yaml

@@ -0,0 +1,12 @@
+appId: com.duckduckgo.mobile.android
+---
+# With the native input field enabled, the NTP shows the native input widget
+# over the omnibar. Tap its back arrow when visible so the regular omnibar
+# (and its menu / text input / icons) is reachable by subsequent steps.
+- runFlow:
+    when:
+        visible:
+            id: 'com.duckduckgo.mobile.android:id/inputModeUnifiedBack'
+    commands:
+        - tapOn:
+            id: 'com.duckduckgo.mobile.android:id/inputModeUnifiedBack'

.maestro/sync_flows/steps/action_add_bookmarks_and_folders.yaml

@@ -4,6 +4,7 @@ appId: com.duckduckgo.mobile.android
 - runScript: script_add_bookmark_domains.js
 # Until here we've joined an account that has predefined data
 # Now, we add a couple bookmarks
+- runFlow: ../../shared/dismiss_native_input.yaml
 - tapOn:
     id: "omnibarTextInput"
 - inputText: "${output.bookmarks.domains[0]}"