Automate patcher binary updates

[RDIL]

We should upload patcher binaries from CI, and ideally make them fully reproducible. Committing the pre-built binary presents a security risk, as it is not clear if it has been tampered with.

[LennardF1989]

With #582 almost through, this is probably a nice one to setup right after.

I propose the following:

• A manual triggered optional job part of the normal workflow
• Job downloads the previously created artifact (https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/storing-and-sharing-data-from-a-workflow#downloading-or-deleting-artifacts)
• Job then proceeds to commit and push the new executable to the current branch the workflow was for. Also see https://stackoverflow.com/questions/57921401/push-to-origin-from-github-action/58393457#58393457

Alternative is that the optional job creates a new PR that needs approving.

What has your preference @RDIL?

[RDIL]

Pushing directly seems fine. The historical reason for committing the binary to Git is so people working on the code can get up and running immediately. I agree we probably don't need to try and update it after every commit.