Change windows release build and sign to use Digicert Keylocker signi…

[moleske]

…ng mechanism

Thank you for contributing to the CF CLI! Please read the following:

• Please make sure you have implemented changes in line with the contributing guidelines
• We're not allowed to accept any PRs without a signed CLA, no matter how small.
  If your contribution falls under a company CLA but your membership is not public, expect delays while we confirm.
• All new code requires tests to protect against regressions.
• Contributions must be made against the appropriate branch. See the contributing guidelines
• Contributions must conform to our style guide. Please reach out to us if you have questions.

Where this PR should be backported?

• main - all changes should by default start here
• v8
• v7

Description of the Change

The old key for signing windows artifacts has expired and digicert changed their method of signing. So this updates it

Why Is This PR Valuable?

Users won't see scary warnings when getting the cf cli on windows

Applicable Issues

List any applicable GitHub Issues here

How Urgent Is The Change?

The key is currently expired, so sooner is better

Other Relevant Parties

Who else is affected by the change?

[pivotalgeorge]

The windows changes in this workflow match the passing signing run within pivotal-cf/cli#windows-signing-via-keylocker-v8, the branch of the repository currently building and signing v8 cli artifacts for release.