Add securebuild release jobs

[divolgin]

Description, Motivation and Context

Please include a summary of the change or what problem it solves. Please also include relevant motivation and context.

Adding SecureBuild to release process.

Checklist

• New and existing tests pass locally with introduced changes.
• Tests for the changes have been added (for bug fixes / features)
• The commit message(s) are informative and highlight any breaking changes
• Any documentation required has been added/updated. For changes to https://troubleshoot.sh/ create a PR here

Does this PR introduce a breaking change?

• Yes
• No

[greptile-apps]

Security Review

The new workflow executes an unpinned, unverified executable selected through releases/latest while exposing the SecureBuild API token. How this was verified: Both build jobs download the mutable artifact and then execute it with the token present in their environment and arguments.

_{Reviews (1): Last reviewed commit: "Add securebuild release jobs" | Re-trigger Greptile}

[greptile-apps]

_{Reviews (2): Last reviewed commit: "Add securebuild release jobs" | Re-trigger Greptile}