fix: deployment script, decouple debugging and deployment settings

[zidaneymar]

Description

fix #2007

1. Fix several bugs of deployment script.
2. Decouple appsettings to appsettings.Devlopment.json(for composer) and appsettings.Production.json(for azure deployment)

Task Item

Screenshots

[boydc2014]

@zidaneymar can you elaborate on the design of decoupling appsetttings.json into dev.json and prod.json? a few questions is

1. is this just for publish or will composer need to write to a appsettings.{env}.json instead of appsettings.json?
2. is this a breaking change? what's the impact here? at least i saw now we need a new arugment to start runtime
3. i see you hard code development.json and prod.json, what if other env?

anyhow, let's get time to address those, and i put an onhold on this one in case accidentally merged.

[zidaneymar]

@zidaneymar can you elaborate on the design of decoupling appsetttings.json into dev.json and prod.json? a few questions is

1. is this just for publish or will composer need to write to a appsettings.{env}.json instead of appsettings.json?
2. is this a breaking change? what's the impact here? at least i saw now we need a new arugment to start runtime
3. i see you hard code development.json and prod.json, what if other env?

anyhow, let's get time to address those, and i put an onhold on this one in case accidentally merged.

1. For now composer will update the customized settings file which is in ComposerDialogs\settings\appsettings.json, I think the root appsettings.json will not be changed by composer, it has many startup parameters for botruntime.
2. This is to fix Response status code does not indicate success: 403 (Forbidden) after Azure deploym,e #2007, previously the deployment script will write the app id, app password, blob storage and other config to the root appsettings.json, if user want to start up the local debugging environment, it will get an 401 unauthorized since the runtime has appid and pwd now.
   So we need to decouple the composer dubugging env(deployment) and deployment env(production) to different files.
3. I'm not sure about the other env, in my understanding we have only two environments for debugging(users could set it as 'composer' but it is still used for debugging) and deployment.

[boydc2014]

do we need to update the protocol to add a new parameter

[zidaneymar]

do we need to update the protocol to add a new parameter

dotnet receive the env parameter to determine whether it's under development

[zidaneymar]

this param will be sent to 'dotnet run' iteself, not a botproject level param.
https://stackoverflow.com/questions/50821504/asp-net-core-set-hosting-environment-in-build-process

[github-actions]

Coverage remained the same at 40.937% when pulling 3bd704b on qika/deployupdate2 into 964b8d6 on master.