[WIP] Malicious website protection - Windows support

[mgurgel]

Asana: https://app.asana.com/0/72649045549333/1208745889841028/f
Reviewer: @shakyShane

Note: Includes #252

Description:

Enables Malicious site protection warnings on Windows

Steps to test this PR:

1. Visit preview
2. Confirm that both phishing and malware states show on Windows

[netlify]

✅ Deploy Preview for ddgdash ready!

Name	Link
🔨 Latest commit	e5f4573
🔍 Latest deploy log	https://app.netlify.com/sites/ddgdash/deploys/67adf0473c2e1e00085c8a77
😎 Deploy Preview	https://deploy-preview-282--ddgdash.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

Temporary Branch Update

The temporary branch has been updated with the latest changes. Below are the details:

• Branch Name: pr-releases/pr-282
• Commit Hash: 904d287af9af5e82ec9ac0006f33f78a36e62dfa

NPM

npm i github:duckduckgo/privacy-dashboard#904d287af9af5e82ec9ac0006f33f78a36e62dfa

Git submodule:

git submodule update --remote --init submodules/privacy-dashboard
cd submodules/privacy-dashboard
git fetch origin
git checkout pr-releases/pr-227
git reset --hard origin/pr-releases/pr-227

Swift

.package(url: "https://github.com/duckduckgo/privacy-dashboard", revision: "904d287af9af5e82ec9ac0006f33f78a36e62dfa"),

[RendijsSmukulis]

I think this should be maliciousSiteStatus = viewModel.maliciousSiteStatus || { "kind": null }; to keep backwards compat with pre-Malicious-site Windows browser version (the Privacy Dashboard seems to crash if this isn't provided)

[mgurgel]

Setting that parameter to null would result in the same state as when the site is considered safe, meaning that in your version of the Windows app, the dashboard wouldn’t wait for the final state of maliciousSiteStatus before rendering, which would cause it to default to safe at first, and then switch to the unsafe state on malicious sites.

Seeing as how this change is only going out with the versions that support it, I think it’s safe to keep it that way. We’ve done the same on other platforms without issue.

If you’re still unsure about keeping it in though, we can discuss alternatives that don’t involve defaulting to null.

[RendijsSmukulis]

Changes look good to me - I made the exact same changes (except for the one commented line at shared/js/browser/windows-communication.js).

Probably still needs @shakyShane 's review, tho