APIOps for one APIM serving as multiple environments

### Question

Hello, I am trying to see if the apiops-cli could be used in this scenario: we use one APIM to serve multiple environments (e.g. dev/test). I plan to create the dev API initially by importing the swagger spec. Now in APIM, the api-id is registered with the imported name (e.g. call it my-dev-api). I want to migrate to a test version within the same APIM. I can use your override configuration yaml to change all the keys I need to. However, I cannot use the same name as the cli apiops publish will just do a PUT to the same API. Am I correct and is there a way to work around this?

### Context

_No response_

Begin with the apiops publish behavior and the override configuration YAML described in the issue; verify whether publishing targets the existing api-id with PUT when moving from dev to test. Done means an explicit supported workflow or documented limitation and workaround for serving multiple environments from one APIM.

Escrito por el modelo de indexación a partir del texto del issue.