Check the `HasConflictWithWpf` flag values

[ameshkov]

We currently have this flag checked for the following AVs due to the old compatibility issues:
Eset
Kaspersky
Malwarebytes AntiMalware
Norton 360
Norton Internet Security

As far as I know, there are no serious issues with ESET and Kaspersky anymore.

So here's what should we do:

1. Conduct a test on Windows 10 with all the listed AVs.
2. Change the default value according to the test result.

How to test:

1. Install both programs
2. Keep an eye on how HTTPS is filtered and if there're any "hanged" connections
3. Try watching a couple of YT videos, if there any issues with connections closing, it is very easy to notice on YT.
4. Reboot the computer (that's important, helps to notice issues).

[confessor-adguard]

As I see, currently we have enabled HasConflictWithWpf only for these antiviruses:

• Malwarebytes AntiMalware
• Norton 360
• Norton Internet Security

Based on Chase message:

ESET EndPoint AV & MalwareBytes Premium

I think we need to check MalwareBytes first.
Then both Norton products.

[adbuker]

resolved in pull-requests/87

[vozersky]

checked both Malwarebytes and Norton, works fine