Rebase tor-browser to esr102.8

Merge Info

• Related Issues

  • tor-browser-build#40725 (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

Mostly straight-forward rebase onto 102.8.

Reviewer should make sure the resolution to tools/update-packaging/make_incremental_update.sh in richard/tor-browser@6b343713 is right.

A couple of patches that we backported early have since been backported to 102.8 (TrustCor revocation, the various 'rU' -> 'r' changes in Python scripts, XPIDL regex) so the diff of diffs looks a bit scarier than is justified. Also some build-breakge to resolve around ShouldResistFingerprinting api changes in the font normalization patch.

range-diff: git range-diff FIREFOX_102_7_0esr_BUILD1..origin-push/tor-browser-102.7.0esr-12.0-1 FIREFOX_102_8_0esr_BUILD1..richard/bug_40725

Doing a local dev build now.