UX: Should confirm before automatically setting a new environment as the default.

[vhvb1989]

From the conversation in : #4561

This issue is about changing the current behavior in azd after a new environment is created. The current implementation is automatically setting the new environment as the default without asking user about it or without even telling user that the new environment has been set as the default.

A new user is surprised, for example, when running azd provision -e new-environment that the next call to azd will continue to use the new created environment, when the intention of using -e flag was to avoid explicitly calling azd env select another-environment.

[Menghua1]

@vhvb1989 We designed a solution to solve this issue, the specific effects are as follows:

• For the azd env new command, the design is as follows:
  

• For azd provision -e new-env, the design is as follows:
  

If you agree with our proposed solution, we will open a PR to fix it.
CC: @rajeshkamal5050

[vhvb1989]

That looks good to me <3
Let me add @kristenwomack and @SophCarp as a heads up and for feedback. I think it is a good change.

[kristenwomack]

Thank you! Looks good.