refactor Command Should Handle Existing Repositories Gracefully

[jmwright]

Currently, the refactor command assumes that the user is pushing the local component to a fresh repository. This won't always be the case. For example, when refacotring an entire project, a soldering iron tool component may have been used in multiple places. The first refactor is the only one that should populate the fresh repository, and the other refactors should alert the user that the repository is not fresh, and simply install the existing soldering iron component from the repository using npm.

This does not address the problem of users modifying the soldering iron component in multiple different places and needing to push changes. That cannot be done from the refactor command, and must be handled by an explicit upload command call.