"Disable resolving of IPv6 addresses" per client basis

### Prerequisites

- [X] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions) and found no answer

- [X] I have searched other issues and found no duplicates

- [X] I want to request a feature or enhancement and not ask a question

### The problem

Apparently, there are some problematic clients that try to connect to IPv6 addresses using the returned AAAA record through their link local ipv6 address when the DNS resolver returns an AAAA record.

User experience is slow loading of IPv6 enabled websites in clients which are IPv4 only, the client connects to the IPv6 website and waits for the timeout.

The usual setup for adguardhome is for a single network only, but there some niche setups wherein a single adguardhome instance is used for two networks, one for IPv6 dual stack and the other could be an IPv4 exclusive network.

Examples
- https://www.reddit.com/r/ipv6/comments/17c5031/some_apps_does_not_work_on_wifi_but_works/
- https://www.reddit.com/r/GooglePixel/comments/15550kf/certain_apps_dont_load_on_wifi_while_working_fine/

### Proposed solution

Make the setting per client instead of per device.

### Alternatives considered and additional information

The current implementation is lacking, as it's global setting, not client basis.
**Edit:** Was able to figure out the custom filtering rule

```
*^$dnstype=AAAA,client=172.16.0.128/25,important
```