Listening to TCP [53] is not working

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

Version: v0.107.48

### Action

In my network im intercepting all the TCP and UDP requests and reidirect them to the Adguard DNS.
This works fine for the UDP but fails on the TCP.

Some applications have hardcoded DNS and when those requests done in TCP Adguard failed to proccess them and application hangs or cant provide data.

For example


An application running in android is making a hardcoded DNS TCP Request to google 8.8.8.8:53

Im redirecting the requests to adguardhome DNS server like i do for UDP


Yet the server doesnt respond back.

This has been happened in previous version as mentioned at: [ Listening to TCP is mandatory in some cases ] #521

### Expected result

Adguard should respond to TCP DNS Requests

### Actual result

No DNS replies

### Additional information and/or screenshots

_No response_