0 byte (\000) seems to cause domain matchig error

### 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, AMD64 (aka x86_64)

### Installation

Docker

### Setup

On one machine

### AdGuard Home version

v0.107.72

### Action

So I just saw in my logs that iahwpf-dnsotls-ds.metric.gstatic.com got blocked by the rule ||metric.gstatic.com^. But then it requested q\000enhk-dnsotls-ds.metric.gstatic.com and no block no nothing, resolved ip, maybe this is a bug caused by the \000 (0 byte) or the backslash in general.

### Expected result

It should have blocked q\000enhk-dnsotls-ds.metric.gstatic.com like normal.

### Actual result

q\000enhk-dnsotls-ds.metric.gstatic.com was not blocked.

### Additional information and/or screenshots