fix: updated condition for adding kubectl apply synced timeline

[kartik-579]

Description

Updated condition for getting/adding kubectl apply synced timeline.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Local Environment
• Microk8s cluster

Checklist:

• The title of the PR states what changed and the related issues number (used for the release note).
• Does this PR requires documentation updates?
• I've updated documentation as required by this PR.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have tested it for all user roles.
• I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
0.0% Duplication

[kartik-579]

RCA: we were updating health status pipeline on basis of reconciliation time and kubectl apply synced timeline. In an edge case, if the sync status changes from succeeded to something else, kubectl apply synced timeline was not getting fetched and this was causing health timeline to not update whereas deployment status was getting updated since we had extra call for kubectl applly synced timeline there.