Renew Windows certificate for code signing

[jay0lee]

The current certificate used to sign GAM .exe and .msi files is due to expire Sept 20th:

signtool.exe verify /pa /v \Users\opt70\Downloads\gam-7.19.01-windows-arm64.msi

Verifying: \Users\opt70\Downloads\gam-7.19.01-windows-arm64.msi

Signature Index: 0 (Primary Signature)
Hash of file (sha256): D4079685B9E1668EEFB3F43E64AB0FC71E051E6497830D938D2E6BC0FA717FE8

Signing Certificate Chain:
    Issued to: Certum Trusted Network CA
    Issued by: Certum Trusted Network CA
    Expires:   Mon Dec 31 08:07:37 2029
    SHA1 hash: 07E032E020B72C3F192F0628A2593A19A70F069E

        Issued to: Certum Trusted Network CA 2
        Issued by: Certum Trusted Network CA
        Expires:   Mon Sep 17 02:43:06 2029
        SHA1 hash: 5F14876473A0EC43DF0AE794A2805FC461125D62

            Issued to: Certum Code Signing 2021 CA
            Issued by: Certum Trusted Network CA 2
            Expires:   Sun May 18 01:32:18 2036
            SHA1 hash: 8D57E2B4008BBE461470A69F3492BC5AE362A7A9

                Issued to: Open Source Developer, James Lee
                Issued by: Certum Code Signing 2021 CA
                Expires:   Sat Sep 20 07:18:45 2025
                SHA1 hash: 590DC5BB10DFB31DBFF38C0E2F9C35EF0F6D0E9E

Expected behavior at that point:

• We won't be able to sign any new files with this then expired certificate.
• Old GAM .exe and .msi files signed with this certificate will continue to verify and work.

I am in the process of getting.a new certificate issued which I should be able to complete before 9/20 and put into place so that there is no interruption with builds.

Current status: working through project verification by Certum before they will issue the certificate (yes, we have to re-verify every year).