[BUG]Duplicate subscriptions created when publishing to multiple environments

Nadie ha tomado este issue todavía.

### Release version

v6.0.1.7

### Describe the bug

When using the APIOps publisher to deploy APIs across multiple environments (e.g., Dev → Test → Prod), subscriptions included in the Git repository result in duplicate subscriptions being created in each environment, even if the displayName and scope are the same.

### Expected behavior

Subscriptions with the same displayName and scope should be treated as the same logical entity and not duplicated in other environments.

Alternatively, subscriptions could be considered runtime-only data and excluded entirely by default, unless explicitly managed.

### Actual behavior

Publishing creates duplicate subscriptions with the same display name but separate keys and internal IDs, leading to confusion and clutter across environments.

### Reproduction Steps

1. Extract from Dev APIM instance using the extractor pipeline — this includes subscriptions/ artifacts.
2. Commit the extracted subscriptions into the APIOps Git repo.
3. Run the publisher pipeline against a different environment (e.g., Test).
4. Observe that new subscriptions with identical displayName are created in Test, instead of reusing or matching existing ones.

Comienza reproduciendo el flujo de extractor pipeline y publisher pipeline descrito para subscriptions/artifacts en Dev y Test. Compara cómo se gestionan en el entorno de destino las subscriptions con el mismo displayName y scope. Done debe definirse como impedir subscriptions lógicas duplicadas o excluirlas de forma predeterminada si ese es el comportamiento elegido.

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