Disables password check feature.

[mkarolin]

Resolves brave/brave-browser#11423

Chromium change:

https://source.chromium.org/chromium/chromium/src/+/e662da68809e7b34e3defa9eb946539a8a0f7ca1

commit e662da68809e7b34e3defa9eb946539a8a0f7ca1
Author: Vasilii Sukhanov vasilii@chromium.org
Date: Wed Jun 10 12:44:20 2020 +0000

Enable 'PasswordCheck' feature on desktop by default.

Additionally the CL introduces the password check flag on Android only.

Bug: 1049177

Submitter Checklist:

• Submitted a ticket for my issue if one did not already exist.
• Used Github auto-closing keywords in the commit message.
• Added/updated tests for this change (for new code or code which already has tests).
• Verified that these changes build without errors on
  • Android
  • iOS
  • Linux
  • macOS
  • Windows
• Verified that these changes pass automated tests (unit, browser, security tests) on
  • iOS
  • Linux
  • macOS
  • Windows
• Verified that all lint errors/warnings are resolved (npm run lint)
• Ran git rebase master (if needed).
• Ran git rebase -i to squash commits (if needed).
• Tagged reviewers and labelled the pull request as needed.
• Request a security/privacy review as needed.
• Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone
• Public documentation has been updated as necessary. 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-issues-with-tracking-protection
  • https://github.com/brave/brave-browser/wiki/QA-Guide

Test Plan:

Reviewer Checklist:

• New files have MPL-2.0 license header.
• Request a security/privacy review as needed.
• Adequate test coverage exists to prevent regressions
• Verify test plan is specified in PR before merging to source

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.

[emerick]

LGTM

[kjozwiak]

Verification PASSED on macOS 10.15.6 x64 using the following build:

Brave | 1.15.12 Chromium: 85.0.4183.83 (Official Build) nightly (64-bit)
-- | --
Revision | 94abc2237ae0c9a4cb5f035431c8adfb94324633-refs/branch-heads/4183@{#1658}
OS | macOS Version 10.15.6 (Build 19G73)

• ensured that Check Password was removed from brave://settings/passwords
• ensure that you can save passwords and they appear under brave://settings/passwords
• ensured that you can login into websites using auto-fill from brave://settings/passwords
• ensured that the Manage button on the modal once you've saved a password works as expected
• ensured that viewing password works as expected once OS authentication is completed
• ensured that clicking on "Details" works as expected
• ensured you can remove the password from brave://settings/passwords via Remove
• upgraded personal profile with ~50 saved passwords and ensured password auto-fill worked as expected
  • ensured that all the above cases worked on an existing profile