Add a function to limit the GB filesize of the query log file

Have a question or an idea? Please search it [on our forum](https://github.com/AdguardTeam/AdGuardHome/discussions) to make sure it was not yet asked. If you cannot find what you had in mind, please [submit it here](https://github.com/AdguardTeam/AdGuardHome/discussions/new).

### Prerequisites

Please answer the following questions for yourself before submitting an issue. **YOU MAY DELETE THE PREREQUISITES SECTION.**

- [x] I am running the latest version (v0.108.0-b.2)
- [x] I checked the documentation and found no answer
- [x] I checked to make sure that this issue has not already been filed

### Problem Description

Currently, the only method to limit the query log size's file, is by the amount of days the queries are stored. This works for 99.9% of AdGuard Home users, but can become a potential problem for those who run [public servers with 100-ish weekly users](https://github.com/DandelionSprout/adfilt/tree/master/Dandelion%20Sprout's%20Official%20DNS%20Server). Keeping the query log time setting set to "30 days", has apparently led to an impressively large log file size of 9.2 GiB, becoming the 2nd-largest single file on my PC.

### Proposed Solution

In addition to the amount of days queries can be stored, it should also be possible to set a max amount of GB (be it Linux-GB or GiB) or MB the file size can reach before the oldest entries are deleted.

### Alternatives Considered

None that I'm currently aware of. Though I should probably have reduced the log days on my setup from 30 to 7 days either way.

### Additional Information

The existing setting for the cache size (which I've set to 40 MB), doesn't seem to affect the query log's size.