[FEAT cloudctl] - Support Dry-Run mode for `sync` command

[onuryilmaz]

[FEAT cloudctl] - Support Dry-Run mode for sync command

Labels

• feature
• safety
• easy-to-use

Priority

(Medium) I'm annoyed but I'll live

User Story

As a cloudctl user, I can run sync --dry-run to see what changes would be made to my local kubeconfig, so that I don't accidentally overwrite important configurations.

Description

The sync command directly modifies the local kubeconfig. A dry-run mode that prints a diff of the changes (clusters added/removed, contexts updated) would greatly increase user confidence and safety.

Acceptance Criteria

• Add a --dry-run flag to the sync command.
• When enabled, do not write to the kubeconfig file.
• Output a summary of proposed changes (e.g., "Would add context: context-a", "Would update cluster: cluster-b").
• Optionally, use hack/compare_kubeconfigs.go logic to show a diff.

Reference Issues

None