[UX improvement] confirmation vs error

[kristenwomack]

The UX here is a confusing. It gives an error message, but the action indicated was successful.

Scenario:

• azd init -t <template-name>
• notification that you're not in an empty directory and asks "continue initializing app here?"
• when selecting no the response is ERROR: confirmation declined which feels indicated that the action I took (answering no) just failed when in fact the intention succeeded

Potential solution:
Provide a positive confirmation that the action of selecting no was successful and you can cd to your intended directory or mkdir for the new app you're initializing.

Brainstorm of potential messages with @SophCarp:

• SUCCESS: confirmation declined; app was not initialized
• SUCCESS: current directory is not initialized
• SUCCESS: confirmation declined
• SUCCESS: app was not initialized

cc: @rajeshkamal5050

[weikanglim]

I think another idea is to remove the error message. This may be slightly more consistent with other tooling.

Or we can have a cancellation indicator if that makes sense

[kristenwomack]

I like both of those suggestions @weikanglim. cc: @SophCarp