Feat: Decouple import operations from apply for pre-existing resources #1410
Description
What would you like to be added?
Currently Kusion server imports resources during the preview and apply operation by adding a importedResources payload that includes a mapping from the Kusion Resource ID to the cloud resource ID.
In this case, Kusion will perform an apply operation, during which it will create a new release whose state will include the pre-existing resources being imported.
This issue tracks the effort to decouple import operation from apply so that import is only creating/modifying a kusion release without going through the apply operation that changes resources in production.
Why is this needed?
An import operation coupled with apply can cause additional risks by making changes to the production environments.