Disable site affiliation fetcher

[fmarier]

Resolves brave/brave-browser#29872

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:

See steps in brave/brave-browser#29872 (comment)

[goodov]

can we add a network audit test for this? if calling some PasswordManager API directly from the code will trigger this, then it would be enough.

[fmarier]

can we add a network audit test for this? if calling some PasswordManager API directly from the code will trigger this, then it would be enough.

Looks like it works indeed. I instrumented the fetching code (where the macro is) and confirmed that without my fix, adding an entry to the password manager in the browser test does trigger the fetch.

So I've added it to the beginning of the network auditor.

[kjozwiak]

Verification PASSED on Win 11 x64 using the following build(s):

Brave | 1.53.4 Chromium: 113.0.5672.53 (Official Build) nightly (64-bit)
-- | --
Revision | 12f5dac35d12e8f4e72d7dd11df557ef93bc046f-refs/branch-heads/5672@{#703}
OS | Windows 11 Version 22H2 (Build 22621.1555)

Reproduced the original issue using 1.53.3 Chromium: 113.0.5672.53 via the STR/Cases outlined via brave/brave-browser#29872 (comment) as per the following:

Using the same STR/Cases outlined above, verified that the Google API network call wasn't occurring as per the following:

Example	Example