Record Issue Build Upstream

The builder read the code and the cause is in one of Marc's services.

tools/rooster_worker/drain.py's FILE-UPSTREAM: marker lands here. NOT a failure and NOT a pull request: the issue leaves the build queue, is tagged for the named service, and is filed to that project on Marc's GitLab through the same issues_service.file_upstream a self-filed finding uses -- so Marc is told, and the reporter sees "waiting on Marc", by machinery that already exists. See issues_service.record_build_upstream for why this door is needed (ISS-541) and what it deliberately does not charge.

422 for a service key the registry does not know: the drain charges that as an ordinary failed attempt so the next builder is told the exact name that was wrong.