If any of the repositories named by git remotes could not be found via
API lookup, a "could not resolve to a Repository" error would be thrown,
but the goal of the base repo logic was to ignore NOT_FOUND errors.
This adds `arhived:false` to the underlying search queries.
Additionally, the query approach was rearranged so that the query
strings are passed as GraphQL variables rather than being interpolated
directly into the GraphQL query string.
Co-authored-by: Mislav Marohnić <mislav@github.com>