[FEATURE] Rewire item dependencies when importing multiple items

Use Case / Problem

When considering using Fabric CLI to deploy fabric items to one or more workspaces, especially in the case of a new tenant or new environment, we might have multiple items that depend on one another. For example, a data pipeline that runs another data pipeline or runs a notebook. Currently, we have to deploy items in dependency order and adjust references (GUIDs for items and workspaces) and update/redeploy.

Proposed Solution

Could we consider improving fab import so that it handles rewiring dependencies when "importing" multiple items?

Alternatives Considered

import items in order and adjust the referenced GUIDs

Impact Assessment

• This would help me personally
• This would help my team/organization
• This would help the broader fabric-cli community
• This aligns with Microsoft Fabric roadmap items

Implementation Attestation

• I understand this feature should maintain backward compatibility with existing commands
• I confirm this feature request does not introduce performance regressions for existing workflows
• I acknowledge that new features must follow fabric-cli's established patterns and conventions

Implementation Notes

No response

Start by locating the fab import command and its handling of item references. Read the existing import flow and tests, then determine how multiple imported items and their workspace or item GUIDs are represented. Done means dependencies are rewired during multi-item imports while existing commands remain backward compatible.