Allow filterlist to use both `Bootstrap` and the `upstream` to resolve a domain for the filter

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

i was trying to make an automated time based temporary allow list, and deployed it within the same docker compose

and whenever i tried to add the API that would generate the correct allow list at that current time it would always says that i can't find the host name of the container

currently the only working solution is to add `udp://127.0.0.11:53` to the upstream dns, i also changed the mode to parallel request temporarily just in case it wasn't resolving the hostname, even after adding the same entry to the `Bootstrap DNS servers` wont resolve the hostname

fortunately I'm the sole user of this dns, and so no one else will be resolving say `dockercontainerhost` to some internal docker address. although I'm not sure if this is a good way to solve the issue if you made this dns available to the public

### Proposed solution

since the filter are technically the internal working of adguardhome it self, i feel like it should also be able to use the `Bootstrap DNS servers` in conjunction with upstream server.

### Alternatives considered and additional information

currently the only alternative solution i found that doesn't require adding "udp://127.0.0.11:53" on the upstream is to bind the external list container to an internal ip, then use that ip as the host to the filterlist instead of the hostname, but doing it this way can be quite annoying to migrate and it's probably not the preferred way of doing things in docker, especially if you want to scale the list provider since the list are not static