Add BadBlock lists

### Prerequisites

- [x] The blocklist is created specifically for DNS-level blockers;
- [x] The blocklist is regularly updated (at least 10 updates per month);
- [x] The blocklist is known and popular;
- [x] The blocklist satisfies [the repo requirements](https://github.com/AdguardTeam/HostlistsRegistry#-what-blocklists-can-be-added-here);

### Blocklist name

BadBlock

### Blocklist category

Ad blocking, Trackers blocking, Malware&phishing blocking, Other

### Homepage

https://badblock.celenity.dev

### Explanation

[BadBlock](https://github.com/celenityy/BadBlock) is a collection of comprehensive blocklists covering a variety of different services, applications, & platforms. Unlike a lot of lists out there, the BadBlock lists are **not** a compilation of other blocklists; entries are carefully considered, found from my own personal research/analysis, and are well documented.

BadBlock additionally includes [whitelists](https://github.com/celenityy/BadBlock#badblock-whitelist). While these whitelists **do** include domains which are common false positives from other blocklists, they're also proactive and ensure that critical domains *(Ex. captive portals/connectivity checks, CDNs, certificate revocation checks, emergency/hotlines, safe browsing, software updates, time servers, visual voicemail, wi-fi calling, etc)* are never blocked in the first place.

In general, I would strongly encourage you to see BadBlock's [README](https://github.com/celenityy/BadBlock) to get a better idea of what BadBlock is and the unique value that it provides.

For reference, BadBlock lists are currently utilized in various other projects, such as [Phoenix](https://phoenix.celenity.dev), [Dove](https://dove.celenity.dev), [IronFox](https://ironfoxoss.org), and [Cromite](https://cromite.org). I've been actively maintaining these lists for over a year now, and plan to continue doing so in the future. I also contribute to other filterlists, such as [HaGeZi's](https://github.com/hagezi/dns-blocklists).

Since we now officially meet AdGuard's [criteria](https://github.com/AdguardTeam/HostlistsRegistry?tab=readme-ov-file#-what-blocklists-can-be-added-here), I would like to propose adding the BadBlock lists to AdGuard's projects, [as requested by users](https://codeberg.org/celenity/BadBlock/issues/25). While the BadBlock project consists of many different lists, I'll specifically focus on and mention the ones that I believe would provide the most value to AdGuard users *(though you're of course welcome to add [any others that seem fit](https://github.com/celenityy/BadBlock).

___

# Blocklists

## BadBlock

**General**

[`BadBlock`](https://github.com/celenityy/BadBlock#badblock-recommended-for-most-people) is the primary, recommended BadBlock list. It's a compilation of various BadBlock lists/sources, and extensively covers advertising, scams/spam, malware, tracking, etc.

## BadBlock Lite

**General**

[`BadBlock Lite`](https://github.com/celenityy/BadBlock#badblock-lite) is similar to the `BadBlock` list above, though it's less aggressive and may be preferable for some users depending on their personal preference.

## Unsafe

**Security**

[`BadBlock - Unsafe`](https://github.com/celenityy/BadBlock#unsafe) is focused on blocking malicious content - ex. adware, badware, malware, phishing, ransomware, scams, spam, etc. Entries from this list are included in **both** `BadBlock` and `BadBlock Lite`, but I believe this would be worth including on its own to allow users to **only** block these malicious domains if they prefer, instead of being stuck with all or nothing.

## Anti-Monitoring

**Security**

[`BadBlock - Anti-Monitoring`](https://github.com/celenityy/BadBlock#anti-monitoring) is focused on preventing the unauthorized monitoring/spying of users - it covers MDMs, Remote Desktop tools, and other undesired monitoring tools. Entries from this list are included in `BadBlock` *(but **not** `BadBlock` Lite)* but for similar reasons as for `BadBlock - Unsafe`, I believe that `BadBlock - Anti-Monitoring` would be worth including on its own to allow users to **only** block these domains if they prefer, instead of being stuck with all or nothing.

___

# Whitelists

## Whitelist

**Other**

[`BadBlock - Whitelist`](https://github.com/celenityy/BadBlock#badblock-whitelist) is the primary, recommended BadBlock whitelist. It's a compilation of the project's various individual whitelists/sources, and includes domains that are used for critical/legitimate functionality - ex. captive portals/connectivity checks, CDNs, certificate revocation checks, common false positives, emergency/hotlines, safe browsing, software updates, time servers, visual voicemail, wi-fi calling, etc.

You can also see all of BadBlock's individual whitelists [here](https://github.com/celenityy/BadBlock#individual-whitelists), and decide for yourself whether you believe they provide value on their own/should be included. I will note that **all** of the individual lists there are included in `BadBlock - Whitelist`.

___

Thank you for your time and consideration, and please let me know if you have any questions or concerns, or need any further information.