Please bring back an option to support AdGuard for Windows users (filter HTTPS excluded pages)

### Prerequisites

- [x] I am running the latest version
- [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

With Adguard for Windows 7.4 and AdGuard Extension 3.5 the integration mode is gone. If I am correct informed, because of an unreliable communication between both. Leaving the user that AGfW and AGE runs both seperately.

AdGuard for Windows contains a big list of excluded pages which won't be filtered.
I already made a ticket here to describe the problem more in detail https://github.com/AdguardTeam/AdguardForWindows/issues/3361 but I think it needs to be integrated in the Extension.

As you can see, I tried to import the HTTPS excluded pages into the Extension, to make the Extension only filtering, when it is one of the HTTPS excluded page. Since I failed, I currently filter pages double in AGfW and AGE :( which can bring some trouble on some rare circumstances: https://github.com/AdguardTeam/AdguardFilters/issues/59086

### Proposed Solution

my idea:

AdGuard for Windows brings automatically a list of HTTPS excluded pages which stays unfiltered.

How about: AdGuard Extension brings the exakt same "HTTPS exluded" list as an option for AGfW users, doing the opposite of AGfW -> instead of "exclude", to "filter only this pages". Both products don't even need to communicate each other as with integration mode before.

Sounds like an inverted whitelist and it absolutely is! But for doing manually, I need need a public list of the HTTPS excluded pages I can import into the Extension. As you can see in the other ticket, I failed by syntax, because some pages needs to have `www.` while other pages not have and the Extension takes care of. But HTTPS exluded list in AGfW doesn't respect the need of `www..`

Hopefully it is not that difficult to integrate, but I might be wrong.

Regards

Start by reviewing the browser extension's existing filtering and integration settings, then compare the linked AdGuard for Windows issue and the reported HTTPS exclusion behavior. Done means there is a documented option for AdGuard for Windows users that applies the HTTPS-excluded-page list with the proposed inverted filtering behavior, without relying on product communication.

Escrito por el modelo de indexación a partir del texto del issue.