Checking out overrides replicate.yaml

[bfirsh]

Problem

Originally discovered by @aanand, but I just ran into this again. If you check out an old experiment with a different replicate.yaml, it overrides your current replicate.yaml and breaks your repository.

This also means you can't migrate repositories to new locations.

Potential solutions

• Don't save / override replicate.yaml (but this stops us from using replicate.yaml for anything else -- e.g. model configuration -- which makes sense to live in the repository)
• Have a separate configuration for repository location, that is never saved into the repository. It could feel more ephemeral, like a Git remote. Perhaps we could encourage people to commit it to Git though, so that Git repositories are linked to Replicate repositories.