Adapt Tor Browser bundling to new HTTPS-Everywhere ID beginning with 5.1.0
The new AMO signing requires changes to the way we bundle HTTPS-Everyhwere. The good thing is if we use the tags as we did everything is fine signature- and version-wise. The bad thing is the EFF needed to change the ID of the self-hosted HTTPS-Everywhere version due to conflicts on the AMO dashboard.
The other change although orthogonal to the AMO signing is moving to a submodule for the translations. We should verify that our build process picks this up.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information