Disable Windows builds on the auto-tester - replace with Azure pipelines

[wilzbach]

We wanted to switch away from the auto-tester for a long time now. However, finding good alternatives has always been tricky and it often was blocked on e.g. a replacement for the FreeBSD testing. Now that the Windows machines are randomly failing again and no one knows why and it's super hard to debug, I think it's more than overdue to start the migration. Over the last months (years?) we have made good experiences with Azure pipelines and they offer 10 concurrent builds for open source projects. It's a stable infrastructure and upgrading to e.g. a newer visual studio build is as easy as changing the VM Image. LDC has been using Azure Pipelines for their Windows testing successfully for a long time as well.

This PR starts to disable the Windows builds on the auto-tester (auto-tester will still fail as the Makefiles need to be disabled on druntime + Phobos too) and adds two Windows builds to Azure with our bootstrapping compiler version (2.079.0).

The other bootstrap builds (Linux, FreeBSD, OSX) can be moved to other CIs later, but for now we want to unblock the broken CI checks.

CC @MoonlightSentinel @andralex @PetarKirov

[dlang-bot]

Thanks for your pull request, @wilzbach!

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "master + dmd#11653"

[MoonlightSentinel]

I assume these changes will break the makefile patching done on the auto-tester?

If that is the case:

• Remove these changes
• Forward MAKECMDGOALS to test/Makefile and do an early exit there

[wilzbach]

Yeah I thought the windows 64 diff had been disabled, but I was wrong :/

https://github.com/braddr/at-client/blob/master/src/do_fixup.sh#L21

[wilzbach]

Failed to compile the `unit` test executable! (exit code 1)

> D:\a\1\s\generated\windows\release\64\dmd.exe @D:\a\1\s\test\test_results\cmdfile
D:\a\1\s\test\test_results\runner.d(6): Error: identifier expected following `package`
D:\a\1\s\test\test_results\runner.d(9): Error: identifier expected following `package`
D:\a\1\s\test\test_results\runner.d(10): Error: identifier expected following `package`
D:\a\1\s\test\test_results\runner.d(11): Error: identifier expected following `package`
D:\a\1\s\test\test_results\runner.d(16): Error: identifier or `new` expected following `.`, not `,`
D:\a\1\s\test\test_results\runner.d(17): Error: found `deinitialization` when expecting `)` following template argument list
D:\a\1\s\test\test_results\runner.d(18): Error: `=` expected following identifier
D:\a\1\s\test\test_results\runner.d(18): Error: declaration expected, not `,`

So it turns out that the auto-tester-test target skipped these unit_tests builds automatically, as they are only interesting to test the compiler API, I think it's reasonable to continue skipping them (they are tested in other Windows builds).

[MoonlightSentinel]

Note that the auto-tester also includes -release in ARGS

[wilzbach]

FYI: this is green on all CIs now 🌮

(except for the auto-tester Windows machines. It requires dlang/druntime#3203 and dlang/phobos#7613 for auto-tester to fully skip Windows build - these three PRs depend on each other)

[wilzbach]

This won't auto-merge as it is interlocked with druntime and Phobos. I will manually merge this and the respective PRs in druntime and Phobos.