Add release jobs to security fork
What does this MR do?
Add release jobs to security fork
Why was this MR needed?
Allow the jobs to also run into our private security fork so we can do releases.
The only exception is development S3
because we don't want to publish
any development binaries that might leak secuirty information before the
vulnerability is disclosed.
Skip the bleeding jobs as well since that will run when we sync the private master branch with the public one and it prevents leaking any information.
What are the relevant issue numbers?
Edited by Steve Xuereb