Feature: Modify app cloning behavior to skip the unreachable pipeline while cloning application

[YashasviDevtron]

🔖 Feature description

We should modifying the app cloning behavior so that if one workflow encounters an error during the cloning process, the remaining workflows should still be cloned. Additionally, we could improved error handling to provide clearer feedback.

🎤 Pitch / Usecases

While cloning an existing application, encountered the following error while cloning a specific workflow:
Error: Get "https://k8s-api-server/api/v1/namespaces/coreos?timeout=30s": dial tcp: lookup k8s-api-server- on xxxxx: no such host.
preventing the successful cloning of the remaining workflows.

🔄️ Alternative

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[vikramdevtron]

@abhibhaw @YashasviDevtron Should we skip the namespace check before creating a pipeline ?

[abhibhaw]

yes @vikramdevtron

[abhibhaw]

I think this was already fixed, pls confirm @vikramdevtron @prakash100198

[abhibhaw]

This has been fixed, parent issue: https://github.com/devtron-labs/sprint-tasks/issues/1546

[prakash100198]

https://github.com/devtron-labs/devtron-enterprise/pull/2368