Async requests with excessively long URLs are causing a blank homepage.

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

GitHub releases or script from README

### Setup

On a router, DHCP is handled by the router

### AdGuard Home version

v0.107.43

### Action

\-

### Expected result

\-

### Actual result

\-

### Additional information and/or screenshots

When accessing the homepage, the page appears blank. Upon inspecting with developer tools, I discovered a `414 Request-URI Too Large` error for the URL `/control/clients/find`. When using nginx as a reverse proxy and having a large number of clients, GET requests carry a significant amount of query parameters, causing the URL to become excessively long and resulting in an error. Although this can be resolved by modifying the nginx configuration, I believe the issue should be addressed within AdGuard Home itself. GET requests should not carry a large amount of data; otherwise, with a higher number of clients, the URL could become even longer, potentially leading to serious problems. Additionally, querying too much data at once should be avoided to prevent performance issues due to excessively large returned data.