Description of problem:
During cluster migration, the managedcluster-import-controller's auto-import feature generates kubeconfigs from both the source hub and target hub simultaneously. These conflicting kubeconfigs override each other, causing:
- Kubeconfig inconsistency during hub switching
- Migration failures
- Cluster connectivity issues

Version-Release number of selected component (if applicable):
Global Hub 1.7.0

How reproducible:
Yes

Steps to Reproduce:
1. Initiate cluster migration from source hub to target hub
2. During migration, both source and target hub's managedcluster-import-controller auto-import feature are active
3. Conflicting kubeconfigs are generated simultaneously
4. Migration fails due to kubeconfig conflicts

Actual results:
- Kubeconfig conflicts occur during migration
- Hub switching fails
- Cluster connectivity issues

Expected results:
- No kubeconfig conflicts during migration
- Smooth hub switching without import controller interference
- Proper cleanup during both normal migration and rollback scenarios
- Consistent cluster connectivity throughout the migration process

Additional info:
- Reference: managedcluster-import-controller auto-import logic
- Fix PR: https://github.com/stolostron/multicluster-global-hub/pull/2202
- Solution involves adding disable-auto-import annotation during initializing stage and removing it during cleaning/rollback stages

🤖 Generated with Claude Code