Go over rebased patches again and reorder pieces where needed after rebase to esr78 is done
We've reordered/squashed bits of our patch set during #31918 (closed). We should do this again once we have the rebasing to esr78 done and are happy with the results.
@acat noted in #33533 (closed): One example that comes to my mind for this is the security level patch, which introduces a localization mecanism which is later replaced by
TorStrings.jsm in the #31286 (closed) patch.
Additionally, there are
firefox-branding.js changes that moved to the updater related patch. We might want to think about something that's less surprising.