Remove problematic filters from OneTrust CMP detection

[seia-soto]

Exception rules were pushed to Ghostery filters (adblocker-filters) but the origin is at TrackerDB.

I don't know removing these rules is a good step for TrackerDB because they're required to detect OneTrust CMPs.

[philipp-classen]

Exception rules were pushed to Ghostery filters (adblocker-filters) but the origin is at TrackerDB.

I don't know removing these rules is a good step for TrackerDB because they're required to detect OneTrust CMPs.

As I understand, the goal is have the rules disabled for NeverConsent. The override to disable them was originally only in adblocker-filters, but when we switched to TrackerDB, they were add to TrackerDB. From that point on the overrides in adblocker filters were no longer needed.

Note that the PR currently would have the opposite effect. Both for detection and whitelisting, having them only in TrackerDB looks best. And in adblocker-filters, we could remove them, since the (negated) rules there should be redundant then.

[seia-soto]

Totally agree. That's the point I wanted to say.