[ Fix ] : Gitops trigger in Save, Delete, and Update Experiment

[Nageshbansal]

Proposed changes

Fixes #4434. This PR adds the checks for gitops update in following handlers

1. SaveChaosExperiment
2. CreateChaosExperiment
3. UpdateChaosExperiment

I think we need to discuss this a little bit more: whether we want the gitops to be triggered while just saving the chaosExperiment or also when a new experiment is scheduled to be running

Types of changes

What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

• New feature (non-breaking change which adds functionality)
• Bugfix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices applies)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have signed the commit for DCO to be passed.
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)

Dependency

• Please add the links to the dependent PR need to be merged before this (if any).

Special notes for your reviewer:

[Saranya-jena]

@Nageshbansal can you check why the backend UT is failing?

[Nageshbansal]

Sure @Saranya-jena checking it now ( missed the comment )

[Nageshbansal]

PTAL @amityt @Saranya-jena @namkyu1999