Support removeparam regexes

[antonok-edm]

removeparam regex rules are relatively uncommon, and should be avoided by filter list authors because of the performance implications of using regexes. However, in some cases they are unavoidable, and so they should be supported.

They were left out of the original removeparam implementation in an attempt to get the majority of the feature released earlier. In particular, uBlock Origin's removeparam implementation requires a special no-op feature to prevent ambiguity when parsing. It's also worth reviewing the regex features supported by JS regexes vs. Rust regexes to minimize compatibility differences.

[krystian3w]

Removeparam can implement better block tracker p.typekit.net: https://github.com/AdguardTeam/AdguardFilters/commit/1ed6c7b58024933f017cc85eb77579779311b65f

then not needed is any allow (at today) or noop.css redirect.

[yokoffing]

Is this in active development? I've like to be able to use LegitimateURLShortener for params, esp. utm.

[antonok-edm]

@yokoffing it's not high on the priority list at the moment, although I could definitely find some time to review if a PR is submitted.

[ghost]

Any roadmap for this?