“badfilter” modifier does not seem to be interpreted

### Prerequisites

- [x] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) and found no answer

- [x] I have searched other issues and found no duplicates

- [x] I want to report a bug and not [ask a question or ask for help](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a)

- [x] I have set up AdGuard Home correctly and [configured clients to use it](https://github.com/AdguardTeam/AdGuardHome/wiki/Clients). (Use the [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) for help with installing and configuring clients.)

### Platform (OS and CPU architecture)

Windows, AMD64 (aka x86_64)

### Installation

GitHub releases or script from README

### Setup

On one machine

### AdGuard Home version

v0.108.0-a.1112+16fda888

### Action

Hi, I've had a problem for a long time, I mentioned it in a discussion earlier this year https://github.com/AdguardTeam/AdGuardHome/discussions/7571

The problem persists, rules with the [“badfilter” modifier](https://github.com/AdguardTeam/AdGuardHome/wiki/Hosts-Blocklists#badfilter) are not interpreted.

I use the [“Badware Hoster blocking”](https://github.com/hagezi/dns-blocklists/?tab=readme-ov-file#hoster) filter from hagezi, but the problem is the same with other filters and rules, personal or otherwise.

### Expected result

The “badfilter” modifier should remain a powerful defence against rules that can be considered as false positives. Today, this asset is reduced to nothing.

It's out of the question to whitelist all subdomains with a rule similar to :
`@@||blogspot.com^`
which would authorize access to the whole domain just because the “badfilter” modifier doesn't work, that's not a valid solution.

### Actual result

In my example, the following rule:
`||blogspot.com^$badfilter`
does not disable :
`||blogspot.com^` present in the hagezi filter
access to Blogspot subdomains (all Blogspot blogs) is still impossible.

This is obviously the case for all the other hosts on this list and all the other rules of this type.

### Additional information and/or screenshots

Thank you for taking this problem into consideration.