chore: introduce testing utility dependency

[KeranYang]

No description provided.

[chandankumar4]

@KeranYang I need to get this #2 PR merged to fix the pipeline failure, after than I can verify this PR changes.

Probably I need to make some change related to deploying moto service, which was done from setup suite in my case. Also redis and e2e-pod is not required but this fixture will deploy that also as it won't harm but taking extra resource and time to run.

[KeranYang]

redis and e2e-pod is not required

Agreed. I am keeping them for now just in case there is future use cases. Will monitor and see if maintaining them increases engineer efforts, if so I will remove them.

[chandankumar4]

If you can resolve the conflict, then we can merge this PR but e2e test will fail, I'll raise another PR to fix it?

[KeranYang]

@chandankumar4 on your next PR, could you remove the dependency on github.com/numaproj/numaflow v0.11.0 ? Let's create our own logger from scratch. The rationale is that numaflow is not a library and UDSink should only depend on numaflow-go sdk.