chore: make prop for deployment app type required in status breakdown component

Author: arunjaindev

src/Shared/Components/AppStatusModal/AppStatusBody.tsx

@@ -192,6 +192,7 @@ export const AppStatusBody = ({
                     isVirtualEnvironment={appDetails.isVirtualEnvironment}
                     appDetails={appDetails}
                     rootClassName="pb-20"
+                    deploymentAppType={appDetails.deploymentAppType}
                 />
             )}
         </div>

src/Shared/Components/CICDHistory/DeploymentStatusBreakdown.tsx

@@ -60,8 +60,7 @@ const DeploymentStatusDetailBreakdown = ({
                     {(
                         [
                             TIMELINE_STATUS.GIT_COMMIT,
-                            ...(appDetails.deploymentAppType === DeploymentAppTypes.ARGO ||
-                            deploymentAppType === DeploymentAppTypes.ARGO
+                            ...(deploymentAppType === DeploymentAppTypes.ARGO
                                 ? [TIMELINE_STATUS.ARGOCD_SYNC, TIMELINE_STATUS.KUBECTL_APPLY]
                                 : []),
                         ] as DeploymentStatusDetailRowType['type'][]

src/Shared/Components/CICDHistory/types.tsx

@@ -522,7 +522,7 @@ export interface DeploymentStatusDetailBreakdownType {
      */
     appDetails: AppDetails | null
     rootClassName?: string
-    deploymentAppType?: DeploymentAppTypes
+    deploymentAppType: DeploymentAppTypes
 }
 
 export interface DeploymentStatusDetailRowType extends Pick<DeploymentStatusDetailBreakdownType, 'appDetails'> {

src/Shared/Components/DeploymentStatusBreakdown/utils.tsx

@@ -230,13 +230,17 @@ const processKubeCTLApply = (
  * This function processes the deployment status details data and returns a breakdown of the deployment status.
  * Cases it handles:
  * 1. If timelines are not present, say the case of helm deployment, we will parse the wfrStatus and put the status and basic deployment info [triggeredBy, deploymentStartedOn, deploymentFinishedOn] into the breakdown data and return it.
- * 2. In case of gitops:
+ * 2. In case of argo_cd:
  *  - There are five timelines in chronological order:
  *    - Deployment Initiated
  *    - Git commit
  *    - ArgoCD Sync
  *    - Kubectl Apply
  *    - App Health
+ *    In case of flux_cd
+ *    - Deployment Initiated
+ *    - Git commit
+ *    - App Health
  *  - Basic flow is we traverse the timelines in order, if find the last status for that specific timeline from response by traversing the timelines in reverse order.
  *  - If element is found, we will parse the status and set the icon, display text, time, etc. for that timeline and set the next timeline to inprogress.
  *  - If element is not found, we will parse on basis of factors like: