Disabling PB on Gmail does not disable Google link tracking redirect removal on Gmail

[ghostwords]

But it should.

Specifically, while our first-party protections content script gets disabled, static and session DNR "redirect removal" redirect rules still run.

To fully disable Google link tracking redirect removal on Gmail (and all other Google sites), you have to disable PB on www.google.com instead. This is not something users can be expected to figure out by themselves.

Problems with Google link tracking removal like #3062 raise this issue's priority.

[ghostwords]

To fix, we could respond to the user disabling Privacy Badger on a Google domain (a site where we perform Google link tracking removal) by disabling "google_redirect_ruleset" static rules, and removing session rules added by registerGoogleRedirectBypassRules().

We would then also update the startup sequence to disable the static rules and skip adding session rules.

We would also want to disable the associated content script, and avoid showing "Link tracking protection active" in the popup.

[ghostwords]

Alternatively, we could make it so that disabling PB on a Google property also disables PB on www.google.com. This is much simpler, but we should consider the downsides.

[ghostwords]

Oh, also, the Google tracking redirect doesn't always go through www.google.com but could be one of the Google country code domains?