Feature: Optimisations required in OSS installation flow.

[abhibhaw]

🔖 Feature description

• [ ] In some case if kubelink gets healthy before orchestrator and thus the connection to orchestrator failed.
• [ ] If any installation of integration fails via devtron stack manager, we still mark it successfully installed and user doesn't have any way to retry installation of integration.
• [ ] If argoCD is already installed in a cluster and devtron attempts to install gitOps integration, it fails and somehow a devtron user is created at the already installed argoCD (Need to verify this again)

🎤 Pitch / Usecases

• [ ] We should implement some retry mechanism for kubelink to retry making connection to orchestrator
• [ ] We should handle the fail scenario's with proper error messaging and retry mechanism
• [ ] We need to handle cases if possible when argocd is already installed on a cluster or atleast error handling if the integration installation failed

🔄️ Alternative

No response

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

• [X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• [X] I have read the Code of Conduct

AB#10012