e.g. foo.git has Neon/unstable /stable /release /release-lts -> raise error if not

It's not clear if this is worth it as we'd have to maintain a whitelist of repos for which that assertion is intentionally not true (e.g. Qt or frameworks) unless T3407 gets fixed

otherwise should be easy. could possibly be done as part of merge or a standalone test which simply does Neon.ls and then ls-remotes all repos. or option is tying this into job updater somehow, that way it'd be more strictly following the actually CI'd repos