Support passing the sha1 of a certificate in Windows codesign

[ccnokes]

• Version: 13.9.0

• Target: Windows, squirrel

Currently, if you want to select a particular certificate to sign a Windows build with, you can use the certificateSubjectName parameter or CSC_LINK. In my organization, the build machine has the certificate stored in the certificate store and is not accessible via the filesystem. The preferred method of selecting a certificate to sign with is via the /sha1 parameter passed to the signtool (documented here: https://msdn.microsoft.com/en-us/library/8s9b9yaz(v=vs.110).aspx). Signing with /n SubjectName is less precise because subject names don't have to be unique and you may have 2 certs with the same name. My organization does for various reasons. Hence, signing with the /sha1 parameter is preferred and used to be supported via the signWithParams option, which was later removed.

I might look at PRing this sometime but thought I'd create an issue here first 😸

[ccnokes]

@develar thanks! You beat me to it. I was working on it last night: ccnokes@c2029a1 😄