The createOrUpdate operation of Key Vault Managed Hardware Security Module should fail when this resource is soft deleted

After tested, I found the createOrUpdate operation of Key Vault Managed Hardware Security Module would always succeed even if this resource is soft deleted. Per my understanding, this operation should fail and throw error message like below this or others when this resource is soft deleted. So could you help take a look this issue? Thanks.

The example of the error:
```
{
"error": {
"code": "ConflictError",
"message": "A KV MHSM with the same name already exists in deleted state. You need to either recover or purge existing KV MHSM."
}
}
```

Begin with the Key Vault Managed Hardware Security Module createOrUpdate operation in the REST API specifications. Use the reported soft-deleted scenario and ConflictError example to determine the expected response contract; the issue names no file or test, so locating the relevant specification and validation coverage is part of the work.

Written by the indexing model from the issue text.