Linux Dedicated publish should perform async deployment

We have seen several reports of deployment timing out in Linux Dedicated because we make `api/zipdeploy` call synchronously.

Usually you'd see the deployment failing initially, then retrying and hitting a `Conflict` as the first deployment is still ongoing in kudu.

We should make the call Asynchronous by calling `api/zipdeploy?isAsync=true` and then poll for the logs. This should help take care of long deployments which is very common if not doing RunFromPackage in Linux Dedicated.

Trace the Linux Dedicated publish path that calls api/zipdeploy and inspect how deployment logs are currently retrieved. Confirm the Kudu behavior for api/zipdeploy?isAsync=true and determine how polling should report completion and failures. Done means long deployments no longer time out or retry into Conflict while preserving useful deployment logs.

Written by the indexing model from the issue text.