if there is a file called metadata.yml.* in backup folder instead of metadata.yml, error out

[sthirugn]

it is common to find metadata.yml.gz for 6.3 and clone identifies the satellite as 6.2

[bbuckingham]

I actually stumbled on this.

A user provided set of backup files to perform a clone. They decided to gzip all files and despite the docs indicating 'metadata.yml' vs 'metadata.yml.gz', I proceeded to attempt a clone with the files as received. The outcome was that it interpreted the clone as a 6.2 install.

The docs were correct; however, it took a couple of iterations to realize that this was the cause of the error.