Add search onboarding exception for BR and AR

[deeppandya]

Resolves brave/brave-browser#26318

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, npm run lint, 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

[SergeyZhukovsky]

++

[tapanmodh]

LGTM

[kjozwiak]

Verification PASSED on Samsung Galaxy S10+ running Android 12 using the following build(s):

Brave | 1.47.46 Chromium: 107.0.5304.91 (Build oficial) canary (32 bits)
--- | ---
Revision | 3d5948960d62418160796d5831a4d2d7d6c90fa8-refs/branch-heads/5304@{#1097}
OS | Android 12; Build/SP1A.210812.016

BR (Brazil) locale (new addition)

Onboarding remove (added into exception list)

• ensured that the default SE for Normal windows is set as Brave
• ensured that the default SE for Private windows is set as Brave
• ensured that tapping on the URL doesn't display the SE onboarding modal (need to tap on the URL on two occasions)

Example	Example	Example	Example

AR (Argentina) locale (new addition)

Onboarding remove (added into exception list)

• ensured that the default SE for Normal windows is set as Brave
• ensured that the default SE for Private windows is set as Brave
• ensured that tapping on the URL doesn't display the SE onboarding modal (need to tap on the URL on two occasions)

Example	Example	Example	Example

FR (France) locale (existing locale with Brave Search as default)

Onboarding remove (added into exception list)

• ensured that the default SE for Normal windows is set as Brave
• ensured that the default SE for Private windows is set as Brave
• ensured that tapping on the URL doesn't display the SE onboarding modal (need to tap on the URL on two occasions)

Example	Example	Example	Example

PL (Poland) locale (doesn't have Brave Search as default)

Onboarding remove (added into exception list)

• ensured that the default SE for Normal windows is set as Google
• ensured that the default SE for Private windows is set as Google
• ensured that tapping on the URL on the second attempt displays the SE onboarding modal without issues
• ensured that Google is selected as the default SE via the onboarding modal
• ensured that both Normal & Private are updated correctly if another SE is selected from the onboarding modal

Example	Example	Example	Example	Example

Selecting another SE from the onboarding and ensuring Normal & Private windows were updated

Example	Example	Example	Example

RU (Russia) locale (Yandex as the default SE)

Onboarding remove (added into exception list)

• ensured that the default SE for Normal windows is set as Yandex
• ensured that the default SE for Private windows is set as Yandex
• ensured that tapping on the URL on the second attempt displays the SE onboarding modal without issues
• ensured that Google is selected as the default SE via the onboarding modal
• ensured that both Normal & Private are updated correctly if another SE is selected from the onboarding modal

Example	Example	Example	Example	Example

Selecting another SE from the onboarding and ensuring Normal & Private windows were updated

Example	Example	Example	Example