Avoid re-cloning registries with `Pkg.Registry.add`

[omus]

If you use Pkg.Registry.add to add an already existing registry the entire registry will be downloaded first before the conflict is noticed:

$ mkdir -p /tmp/julia-depot
$ export JULIA_DEPOT_PATH=/tmp/julia-depot JULIA_PKG_SERVER=""
$ time julia -e 'using Pkg; Pkg.Registry.add("General")'
     Cloning registry from "https://github.com/JuliaRegistries/General.git"
       Added registry `General` to `/tmp/julia-depot/registries/General`
julia -e 'using Pkg; Pkg.Registry.add("General")'  26.10s user 7.72s system 80% cpu 41.826 total

$ time julia -e 'using Pkg; Pkg.Registry.add("General")'
     Cloning registry from "https://github.com/JuliaRegistries/General.git"
Registry `General` already exists in `/tmp/julia-depot/registries/General`.
julia -e 'using Pkg; Pkg.Registry.add("General")'  26.37s user 11.05s system 86% cpu 43.262 total

[omus]

Mainly this is an issue for CI. Specifically if you were to use julia-actions/cache with registry caching and later use julia-actions/julia-buildpkg the Pkg.Registry.add("General") call in that action can result in wasting time cloning a repository that is already present on disk.

[KristofferC]

Fixed by cf6191b#diff-207055bf1cfbe124497d7079ce1ffb06c549f3534fc7b0988b2051fd1a74f1c2R177-R179.

❯ time julia +nightly -e 'using Pkg; Pkg.Registry.add("General")'
julia +nightly -e 'using Pkg; Pkg.Registry.add("General")'  0.24s user 0.05s system 96% cpu 0.302 total