feat: $removeparam

[seia-soto]

This adds experimental $removeparam support for adblocker: https://github.com/gorhill/ublock/wiki/static-filter-syntax#removeparam

The suggested matching process changed by this PR is illustrated as follows:

1. $important (not subject to exceptions)
2. redirection ($removeparam and $redirect=resource)
3. normal filters
4. exceptions

The removeparam filter priorities are as the followings, and also described in the exception test as a code:

Details

• s1) global removal + exception => global removal wins

@@||example.com$removeparam=utm
||example.com$removeparam

result.filter=global removal
result.exception=(none)

• s2) removal + global exception => exception wins

||example.com$removeparam=utm
@@||example.com$removeparam

result.filter=removal
result.exception=global exception

• s3) removal + exception => exception wins

||example.com$removeparam=utm
@@||example.com$removeparam=utm

result.filter=removal
result.exception=exception

---

0. global exception
1. global removal
2. exception
3. removal

TODO

• Parsing regex as value (in separate PR with refactor and clean up of regex util funcs)

[chrmod]

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/declarativeNetRequest/URLTransform

[seia-soto]

Note: we're going to apply filters one by one

[seia-soto]

Leaving a note: regexp wrapping: [\\?&](${value!.slice(1, flagSeparatorIndex)}[^=]*)

[chrmod]

Does this support exceptions like $removeparam=igshid,domain=instagram.com|threads.net?