Change order of arguments to signtool.exe.

According to the documentation at https://docs.microsoft.com/en-us/dotnet/framework/tools/signtool-exe,
any options should be coming before the `file_name`, denoting the file
to be signed.

This should stop the options being seemingly ignored, and causing issues
during the release process.

Author: NlightNFotis

.github/workflows/release-packages.yaml

@@ -207,7 +207,7 @@ jobs:
           $servers = @('http://ts.ssl.com', 'http://timestamp.digicert.com', 'http://timestamp.sectigo.com')
           foreach($ts_server in $servers)
           {
-            & signtool.exe sign /f $env:pfxcert /p "${{ secrets.CODESIGNCERTPASSWORD }}" /tr $ts_server ${{ steps.create_packages.outputs.msi_installer }} /td SHA256 /fd SHA256
+            & signtool.exe sign /f $env:pfxcert /p "${{ secrets.CODESIGNCERTPASSWORD }}" /tr $ts_server /td SHA256 /fd SHA256 ${{ steps.create_packages.outputs.msi_installer }}
             if ($LastExitCode -eq "0")
             {
               # Stop if code-signing the binary using this server was successful.