Remove search onboarding from In

[deeppandya]

Resolves brave/brave-browser#28656

Submitter Checklist:

• I confirm that no security/privacy review is needed, or that I have requested one
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally:
  • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
  • npm run lint, npm run presubmit wiki, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on
• All relevant documentation has been updated, for instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Custom-Headers
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

[sujitacharya2005]

LGTM

[tapanmodh]

lgtm

[kjozwiak]

Verification PASSED on Pixel 6 running Android 13 using the following build(s):

Brave | 1.50.75 Chromium: 111.0.5563.41 (Official Build) canary (32-bit)
--- | ---
Revision | 976ef12907ef9b413c2d929c043307b415d27b9e-refs/branch-heads/5563@{#737}
OS | Android 13; Build/TQ1A.230205.002

Basically ensured that tapping on the URL bar on a clean install didn't launch the SE onboarding like we're currently doing with 1.48.x. Went through the following:

Test Case #1 - India

• changed the device locale/language to India
• installed/launched 1.50.75 Chromium: 111.0.5563.41
• tapped on the URL and ensured that Brave Widgets was the first onboarding that appeared
• ensured that tapping on the omnibox the second time around didn't launch the SE onboarding
• ensured that there's no SE onboarding when tapping on the omnibox after several restarts
• ensured that Brave was selected as the default SE for both Normal and Private windows/tabs

screen-20230301-133622.mp4

Example	Example	Example	Example

Test Case #2 - Other Locales that have SE onboarding (Japan & Russua)

• changed the device locale/language to Japan & Russia
• ensured that onboarding is still appearing when tapping on the omnibox after the Brave Widget onboarding appears

Japan	Russia