Fix build pipeline and test cases for chaos-operator and litmus-go

[uditgaurav]

Proposed changes

Summarize your changes here to communicate with the reviewers and make sure to put the link of the related issue

How has this been tested:

• Test environment
  • GKE
  • AWS
  • OpenShift
  • KinD/k3s/k3d cluster
  • Others
• Tested with production environment ( For ChaosCenter Tests )
• Have not tested

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.
• I have added necessary documentation (if appropriate)
• I have added Screenshots or Terminal snippets in the PR comment to validate the successful execution of changes

Documentation

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• data-cy=* parameters have been added in codebase ( ChaosCenter Tests )
• data-cy=* parameters need to be added in codebase ( ChaosCenter Tests )
• No updates required.

Code Review

• Does the test handle fatal exceptions, ie. uncaught exceptions from 3rd party library (if any)

Issue

• Audit and Resolution of Pipeline Failures Across LitmusChaos Repositories litmus#4605

Dependency

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

Special notes for your reviewer: