Add Release CI on tag to build release binaries

[EliSauder]

Pull Request Type

• Bug fix
• New feature
• Code style / formatting / renaming
• Refactoring (no functional or API changes)
• Build / CI related changes
• Documentation
• Other (please describe):

Related Issue

Issue number: N/A

Current Behavior

Releases are manually created (as far as I can tell) and only the mac/windows binaries are provided.

New Behavior

On tag, builds and tests windows/darwin/linux arm/amd builds of osslsigncode as staticly linked binaries that get added to a release draft for the tag.

Scope of Changes

• Added: .github/workflows/relase.yml - Enables the release workflow
• Modified: cmake/SetCompileFlags.cmake - /CETCOMPAT is only supported on intel processors. Conditionally disabled it on arm.
• Added: .github/workflows/patches/cetcompat-arch-guard.patch - Applies the SetCompileFlags.cmake patch to tags that don't have it (this way prior releases 2.10+ can be built).

Testing

• Existing tests
• New tests added
• Manual - See my fork for example releases and the action runs. https://github.com/EliSauder/osslsigncode/releases

Additional Notes

Compatible with version 2.10+ Releases
Statically Linked - This was chosen to work nicely with hermetic build systems like bazel.
Arm Support - As someone who has owned arm devices and had to fight to get support, I always try to include it where possible.

License Declaration

• I hereby agree to license my contribution under the project's license.

[EliSauder]

Alright, I have tested the CI run (https://github.com/EliSauder/osslsigncode/actions/runs/32870305758) everything is green.

I also moved away from the venv that is in the base ci.yml file since I've had more problems then benefits with it. And since everything is in an ephemeral build environment, should be fine to not use it.