[AppService]Kudu Jar deploy in windows container failed

Kudu jar deploy with parameters `restart=true&isAsync=true&trackDeploymentProgress=true` in windows container will suspend for quite some time and finally fail with deploymentStatus `RuntimeFailed`. But when we restart the app after deployment failure, it's up and running.

Meanwhile, getting deployment status via `/Microsoft.Web/sites/{appName}/deploymentStatus` returns:
```json
"properties" : {
"deploymentId" : "REDACTED",
"status" : "RuntimeStarting",
"numberOfInstancesInProgress" : 0,
"numberOfInstancesSuccessful" : 0,
"numberOfInstancesFailed" : 0,
"failedInstancesLogs" : [ ],
"errors" : null
}
```
Notice the `numberOfInstancesInProgress` is 0, seems no deployment is being carried out.

No issue experienced in linux container.

Start by reproducing the Kudu jar deployment with restart=true, isAsync=true, and trackDeploymentProgress=true in a Windows container, then compare its deploymentStatus response with the Linux behavior. Done means the Windows deployment completes successfully without requiring an app restart and the status reports meaningful instance progress or failure details.

Written by the indexing model from the issue text.