Bug 41636, Disable back webextension.storage.sync after ensuring NoScript settings won't be lost

Merge Info

• Related Issues

  • #41636 (closed)

• Backport Timeline

  • Immediate - patchsets for critical bug fixes or other major blocker (e.g. fixes for a 0-day exploit) OR patchsets with trivial changes which do not need testing (e.g. fixes for typos or fixes easily verified in a local developer build)
  • Next Minor Stable Release - patchset that needs to be verified in nightly before backport
  • Eventually - patchset that needs to be verified in alpha before backport
  • No Backport - patchset for the next major stable

• Upstream Merging

  • Merge to base-browser - typically for !fixups to patches in the base-browser branch, though sometimes new patches as well
    • NOTE: if your changeset includes patches to both base-browser and tor-browser please please make separate merge requests for each part

• Issue Tracking

  • Link resolved issues with appropriate Release Prep issue for changelog generation

Change Description

This just reverts fa845a8b, now that NoScript 11.4.18 is publicly available on AMO and doesn't forget its settings anymore even if sync storage gets suddenly disabled (like we accidentally did some weeks ago, #41633 (closed)).

No need to backport because we didn't apply the temporary work around to stable (it was too late).