Windows exe certificate serial number doesn't match docs for 1.19.1 release

[gregsskyles]

I followed the instructions in docs/security/verify-installers.md with respect to Windows executables with the file from the 1.19.1 release page and don't see the expected serial number (for either of the two signatures found in the exe).

• Documented: For releases since July 14, 2022: d77e4f8b938f56ae265cd08e9193490c
• Actual (Microsoft issued signature): 33000852bd6c3a151ff92180ee0000000852bd
• Actual (Actalis issued signature): 0546d987b1f62925d8c96672c9bb8ea0

I'd submit a PR to updated the expected serial numbers, but I don't know that they have changed, or what the 'since' date would be in that case. Since the gpg signature verified with the asc file provided in the release, I'm guessing the exe file is good, and the Windows code signing signatures have been updated at some point since 2022.

[infeo]

With Cryptomator 1.18.0, we changed our signing process from a single, long time signing certificate to shortlived certs, meaning every release is signed with new certificate (with a different serial number).

So, i guess we need an entry for every new release.

[infeo]

@gregsskyles We welcome a PR. Can you update the list with the new cert serial ids for every new stable version? (currently 4: 1.18.0, 1.18.1, 1.19.0, 1.19.1)

[gregsskyles]

Sure, I'll take a stab at that.