[BUG] behavioral change for deployment status of Web App deployment slot OneDeploy

### API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/web/resource-manager/Microsoft.Web/stable/2023-12-01/WebApps.json#L12164

### API Spec version

2023-12-01

### Describe the bug

Customer reported from SDK: https://github.com/Azure/azure-sdk-for-java/issues/41478

After OneDeploy(url and parameters: https://571395cd02-slot51181.scm.azurewebsites.net/api/publish?type=jar&isAsync=true&trackDeploymentProgress=true) for deployment slot, we can only get `BuildSuccessful`, not `RuntimeSuccess`. Previously for both WebApp and WebApp deployment slot, we'll get `RuntimeSuccessful`.

### Expected behavior

For deployment slot, we should be able to get `RuntimeSuccessful`.

### Actual behavior

For deployment slot deploy, we can only get `BuildSuccessful`.

### Reproduction Steps

1. Create WebApp with linux plan and Java11
2. Deploy Jar through https://571395cd02-slot51181.scm.azurewebsites.net/api/publish?type=jar&isAsync=true&trackDeploymentProgress=true
3. continuously get deployment status through https://github.com/Azure/azure-rest-api-specs/blob/main/specification/web/resource-manager/Microsoft.Web/stable/2023-12-01/WebApps.json#L12164
4. Stuck at `BuildSuccessful`. Never reached `RuntimeSuccessful`

### Environment

_No response_

Start with the deployment-status definition at WebApps.json#L12164 and compare the reported slot behavior with the documented status values. Reproduce the flow using the supplied OneDeploy URL and continuously query the deployment-status endpoint. Done means a deployment slot reaches RuntimeSuccessful rather than remaining at BuildSuccessful.

Written by the indexing model from the issue text.