Add missing Edge 13 data based on Confluence

[foolip]

Produced by npm run confluence -- --fill-only --browsers=edge with
local changes applied to only include changes where the new version
was 13. Since Edge 12 was the first version of Edge and we don't have
data for Edge 12, this means we can't know if these APIs were first in
Edge 12 or Edge 13, so it can only say true.

[foolip]

@Elchi3 can you review?

[foolip]

@patrickkettner this is the PR I asked about. In https://en.wikipedia.org/wiki/Microsoft_Edge#Release_history it appears that there was a stable release of Edge 12, there is a fair bit of "version_added": "12" in the data currently. Given this, if we have data from Edge 13 but not Edge 12, is it best to use 13 or true to represent this?

If there's some way to get hold of an Edge 12 build that would be cool of course.

[foolip]

I did a bit of looking around for old versions of Windows 10, and based on https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/how-to-get-an-older-windows-10-iso-eg-build-1511/ff09c5af-0932-4459-8048-17f638d6f87f it seems unlikely one can get hold of Edge 12 still.

[saschanaz]

IMO too many new trues here, we could do <=13 or something if we had a solution for #3021.

[saschanaz]

@foolip Microsoft still somehow serves the old build 10240, here's how to get it: https://www.intowindows.com/download-windows-10-rtm-esd-iso-from-microsoft-now/

[foolip]

I'd be happy to do <=13 if that were possible. I'll see if I can get that image working though.

[foolip]

I've been able to collect data from Edge 12 in mdittmer/web-apis#75. I'll close this PR and open another that takes that data into account.

[Elchi3]

Thanks so much @foolip! 🎉

[foolip]

Edge 12 data in #3392.