[BUG] container app revision spec is missing running states

[weikanglim]

API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/app/resource-manager/Microsoft.App/stable/2024-03-01/ContainerAppsRevisions.json

API Spec version

2024-03-01

Describe the bug

On Azure Developer CLI team, we were trying to implement a feature to wait for a revision to be ready. In testing, we found out that there are terminal states that are not being captured.

For example, ActivationFailed is a state we found that was not captured.

Expected behavior

RunningState should have all enum values captured in the API spec, otherwise clients will not know how to handle all applicable states.

Actual behavior

RunningState is missing values such as ActivationFailed.

Reproduction Steps

We had a container that had failed with VolumeMountFailure, and that resulted in an ActivationFailed state that isn't captured in the current list here.

Environment

No response

[zzhxiaofeng]

@Juliehzl Please help have a look, thank you.