[abp-ie] Set up a Windows build server

[fhd]

Background

We currently have to build ABP for IE devbuilds locally. We should really build them automatically instead, as we do on other platforms.

What to change

This has two parts: First we need to set up a server that has all the prerequisites for building ABP for IE. Next we need to hook this up to the nightly build mechanism we have. It's probably easiest for now if we just regularly schedule a build and upload on that server, until we have a CI server.

[trev]

Note that we already produce Android builds on a separate server (quite an ugly hack right now). It calls an SSH command on the remote server and gets a build back. The main problem with this approach (other than the amount of hardcoding): we don't run builds in parallel. So a lengthy build process will delay building of all other development builds. That's the main reason why our Android builds depend on libadblockplus-binaries rather than libadblockplus directly. IE builds have the same issue, they take a while.

[fhd]

Yeah, that's why I suggested we schedule builds on the Windows build server instead of having them triggered by the main server. We can use longer intervals for now, even just one build per day would be better than none at all, which is the current state.

[fhd]

Removing dependency on #1281 and making it dependent on #5133 - Windows builds for libadblockplus and adblockplusie should be a very similar/connected affair.

[fhd]

As discussed in #5133, it's actually not as easy as I thought, the way the build process works, we can't just produce non-signed binaries and sign them elsewhere, we need to sign them in the middle of the process.

So I've removed #5133 as a dependency again. But I'm also not re-adding #1281, since we are moving away from the idea of having a single centralised build infrastructure. It'd be OK to have an adblockplusie specific system.