Disable motion sensors and background sync by default

[fmarier]

Fixes brave/brave-browser#4709 and brave/brave-browser#4789.

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-Protection-Mode
  • 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:

For background sync:

1. Load https://deanhume.github.io/Service-Workers-BackgroundSync/
2. Open the devtools console.
3. Press the "Make an HTTP request - do it!" button.
4. Look for "Unable to fetch image." in the console (and not "sync registered").

For either feature:

1. Load https://brave.com
2. Click the padlock icon in the URL bar.
3. Click "Site settings".
4. Look for "Motion sensors" and "Background sync". They should both be labeled "Block (default)".

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.
  • Update https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove).

[bsclifton]

Adding @bridiver to review, since this involves patching

Taking a look myself, not sure how to avoid patching in a clean way (as Register will throw a DCHECK if you try to call it twice with the same key)

[bsclifton]

Test plan works great! Change looks good to me. Let's wait until @bridiver can review before merging 😄

[bridiver]

see comments

[bsclifton]

cc: @fmarier per the feedback above (also needs a rebase)

Addressed in the latest revision.