Azure code signing for windows

[daschuer]

This uses my new Remote Code Signing Certificate on Azure.

The PR has no Access to the Secrets, but my private build works:
https://github.com/daschuer/mixxx/actions/runs/7311877284/job/19921895739

[JoergAtGithub]

mixxx.exe is signed, but none of the DLLs (with exception of vcruntime140.dll, which is provided as signed binary by Microsoft).
I'm not sure, if this is neccessary, because my Windows Firewall settings are higly customized.

[JoergAtGithub]

Suggested change

	- name: "[Windows] Sign binaries"
	- name: "[Windows] Sign executables"

[JoergAtGithub]

or "executable binaries"

[daschuer]

I have added a code siging PR for the DLLs here: mixxxdj/vcpkg#108

[fwcd]

Just a side note, should this target 2.4?

[daschuer]

Of cause ... Done

[JoergAtGithub]

Should we merge this now, or should we wait for the buildenv PR with signed DLLs?

[daschuer]

We can merge this now. There is nothing else to do than switch to the environment for the signed DLLs.
By the way in 2.3 the DLLs are also not signed.

[JoergAtGithub]

Then let's merge this.
Then we should get Beta builds for Windows again. I'm curious what other user report - because my system is configured in a way, that it never claims about unsigned Mixxx builds.
Thank you!

[ronso0]

Thanks @daschuer fo all this tedious, not very thrilling work on the build system lately!