CLI: Improve UX for Component Overwrites

[huntabyte]

Describe the feature

Today, if you add the <Button> to your project and customize it and then later add a component that depends on the <Button>, the contents of the <Button> will be overwritten.

This makes sense, considering we make changes to the component for some dependencies to accommodate a new one. However, we don't give any messaging around this happening.

I'm thinking at the very least, we throw up a confirmation letting the user know - These dependencies will be overwritten, continue (y/n). But the question is, what do we do when they say no, do we not add anything at all? Or do we simply skip updating those dependencies?

Alternatively, we could say something along the lines of Component X depends on components Y, and Z, which you have previously added. These components may have been updated blah blah blah. Do you want to overwrite them now? (y/n) - if the user selects no, then we could say something along the lines of, You've opted not to overwrite these components; please manually diff the latest to ensure you aren't missing any functionality..

The last idea is to let them know that already added components will be overwritten and their git working tree isn't clean, and to ensure they commit beforehand.