cloud-atomic: Bring sanity to the remote setup
    
    We were doing gyrations here between the "installmedia" remote and the
    intended "fedora-atomic" remote.  Thinking about this, it's *far*
    simpler if we pretend installmedia is the target remote.
    
    We still need to delete the remote configuration Anaconda added and
    re-add it with the real target URL.
    
    Conflicts:
    	fedora-cloud-atomic.ks