Linking multiple APIM instances as environments should generate deployments, not duplicate APIs.

# What are you trying to achieve?

Trying to use API Center as an inventory to understand where each API is in the lifecycle, based off multiple linked APIM instances. Each APIM instance represents an environment (DEV, QA, etc).
Currently if an API exists in multiple linked APIM instances, there will be duplicate entries of the API in API Center, each with their own separate versions and deployments.
I would have expected these to link up automatically when using the MS APIOps approach.

# Proposed solution

API Center should detect when an API being synced from an APIM instance has already been created from another linked instance. If so, the existing API should be auto-updated with a new deployment in the other synced APIM instance's environment in API Center. As opposed to creating a second duplicate API record.

# Alternative solutions

The only alternative I am aware of is keeping only one linked APIM instance that will sync API definitions from a DEV environment, and maintaining deployments for each next deployed environment on the API using scripts in pipelines.