nice thanks for fixing this up - see API suggestion but I don't feel strongly - depends on how much we think dagit needs to know about the specifics of these repositories.
part of me wonders if in graphql this should just be exposed directly as key-value metadata like it was before on codepointer - since they're all presented equally and we do seem to change them frequently
Like if we add docker origins in the future or something, maybe it just exposes key-value pairs here? just something to consider
consider keeping the metadata key-value pairs from code pointer here?