Post #2070600

@loadhigh During some debugging of the build process someone tried to make the logging more verbose, which.. worked a little too well and also affected the step in which the singing key gets imported. We've addressed this for the future by restricting a lot more on which CI runs the singing key is actually available. We've also learned, that while Forgejo is technically supposed to redact any CI log output that matches a secret, this doesn't work well with multi line secrets. (still need some time for more testing on this to do a proper Forgejo PR)