Replace requests to laptop-updates.brave.com with requests to usage-ping.brave.com and feedback.brave.com

[DJAndries]

Resolves brave/brave-browser#16374

Submitter Checklist:

• I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
• 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 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/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

Use a MITM proxy to ensure that usage pings are sent to usage-ping.brave.com and Android feedback is sent to feedback.brave.com. On Windows, rename the installer to Brave-Browser-BRV002.exe. Use the proxy to ensure a one-time request is sent to https://usage-ping.brave.com/promo/initialize/nonua with the refcode (BRV002) included in the body.

[petemill]

Instead of adding another build flag variable for the referrals server, couldn't this use the existing brave_domains::GetServicesDomain(string key) function, which will take a prefix ("usage-ping" or "referrals" in this case) and add the correct domain suffix according to the build environment or cli param overrides.

[DJAndries]

good point, i forgot about that function. let me swap that out.

[bridiver]

@kylehickinson @Brandon-T we should export BraveServicesDomain to ios

[bridiver]

also hard-coding these url defeats the purpose of not including them in the gn config by default

[brave-builds]

Released in v1.73.28