Support cosmetic filterlists

[muodov]

This PR adds the optional support for cosmetic filterlist rules. Note that they are only used as a fallback, when autoconsent rules are not available for the given site. Autoconsent rules are still preferred as they can actively click reject buttons.

• Currently, we are using Easylist Cookie list, and it's bundled into the source code for performance reasons. Building with another filterlist is fairly simple, but we don't provide an official API for this at the moment.
• The test browser extension bundles the filterlist by default. To use the filterlist in the library, you need to use the correct import path (see below), and set enableFilterList config to true.

Breaking changes:

• the exports of the npm package are now limited to the following endpoints:
  • import AutoConsent from '@duckduckgo/autoconsent' will import the main library class. This was the main use-case before, so most likely your code will not break.
  • import AutoConsent from '@duckduckgo/autoconsent/extra' will import the same class with a bundled filterlist. While it will increase the site coverage, it will also significantly increase the bundle size.
  • import rules from '@duckduckgo/autoconsent/rules/rules.json' will import the JSON rules. This is added mainly for backward compatibility.
• All exports support CommonJS and ESM, so you can use require() too.
• If you need to import another source file directly, you can still do it by the full path, e.g. import DomActions from './node_modules/@duckduckgo/autoconsent/lib/dom-actions.ts'

[sammacbeth]

Looks good - just a couple of minor changes I think would improve it.