Another bunch of potential trackers missing

I've added a new virtual column to my tracker table and found that there are 104 entries which are not covered by Exodus. Table data are based on definitions by Appbrain plus from my own scanner. Condition for the virtual column `is_tracker` is:

```sql
case when exodus_id is not null OR category='ats'
OR tags like '%_ads,%' OR tags like '%,analytics,%' OR tags like '%,mediation,%'
OR types like '%,ad,%' OR modwarn_id is not null then 1 else 0 end
```

So I did a `select * from libs where is_tracker=1 and exodus_id is null;` using the `INTO OUTFILE` clause of MariaDB (sorry, the JSON functions are not yet available in 10.0 – and no, I cannot simply upgrade but will do eventually). I've added a header line, and attached the results as `.gz` here:

[zz_exodus.csv.gz](https://github.com/Exodus-Privacy/etip/files/4683892/zz_exodus.csv.gz)

I guess not all of them are worth being added (some are almost completely unknown/unused) – but things like `amazon_aws_metrics` or `amazon_mobile_analytics` probably are :wink:

Related for reference: #31

Start by reviewing the attached zz_exodus.csv.gz and the SQL condition in the issue, then compare the listed entries with the existing tracker data. Decide which candidates warrant coverage, with particular attention to the examples named in the report; done means the selected missing trackers are appropriately added or otherwise accounted for.

Written by the indexing model from the issue text.