Add operator interface for Probe pkg

[sukkyun2]

Proposed changes

This PR adds operator interface to probe pkg

#4836, I tried to add fuzz test for probe handler.
However, the current architecture made it impossible to mock probe operations, so I added probe operator interface.

This picture is about probe pkg.

References

• Update the code architecture to Interface model for Environment pkg #4159
• Testing-Strategies-for-Contributors

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:

I need feedback on the approach of passing probeOperator as a parameter to functions.

For example, the function GenerateExperimentManifestWithProbes in chaoscenter/graphql/server/pkg/probe/utils/utils.go directly accesses probe operation. I have added the probeOperator dependency to the handler that uses GenerateExperimentManifestWithProbes and updated the function calls to pass probeOperator as a parameter.

[namkyu1999]

can you check a build-pipeline? @sukkyun2

[S-ayanide]

Rather than passing the operator as a parameter, better to add this to the Probe Service and then use it like so

func (p *probe) GenerateExperimentManifestWithProbes ... {
    p.probeOperator.GetProbeByName
}

Otherwise every instance of this handler would require you to declare and pass on this probeOperator like this
something := GenerateExperimentManifestWithProbes(..previous params, interface.probeOperator)

The better approach would be to use this handler via the service
something := c.probeService.GenerateExperimentManifestWithProbes(..previous params)

Its easier to test in the long run, the test cases would actually be used as checkpoints with this approach. Which also means that the respective initializers would need to change. For example for the above

type experimentRunOps struct {
	...previous values
	probeService  probeService.Service
}

func NewExperimentRunOps(...previous values, probeService probeService.Service) ExperimentRunOps {
	return &experimentRunOps{
		...previous values,
		probeService:  probeService,
	}
}

[sukkyun2]

I’ve made the changes as suggested. Thank you for the feedback.

[S-ayanide]

Same review for this, could be added to the Service interface and used like the above