/etc/hosts style custom filtering rule mis-described in query log

### 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)

Linux, ARM64

### Installation

Docker

### Setup

On one machine

### AdGuard Home version

v0.107.57

### Action

### Setup

### Test 1

```
$ dig @localhost +short test.home.arpa
192.168.132.100
```

### Query log 1

### Expected result

That:

* "Test 1" would return the expected response to the query; **and**
* "Query Log 1" would report that the query **not** blocked.

### Actual result

"Test 1" shows the expected response to the query (ie the query was **not** blocked) but "Query Log 1" reports that the query **was** blocked. It's a contradiction in terms.

### Additional information and/or screenshots

When I noticed that "Test 1" was succeeding while "Query Log 1" was reporting that the query was blocked, I wondered what would happen if I explicitly unblocked the query.

### My reaction


Click "Unblock". The result is:

### Test 2

```
$ dig @localhost +short test.home.arpa
$
```

Silence indicates no response.

### Query log 2

### Summary

"Test 2" indicates the query was blocked while "Query Log 2" erroneously suggests the query succeeded.

When it comes to using `/etc/hosts` style custom filtering rules, it looks to me like AdGuardHome has things back-to-front.