Use separate module names for the client-go and api pkgs from the operator implementation

[ahg-g]

What would you like to be added:

Allow developers to import the LWS api and client-go pkgs without the operator implementation.

Why is this needed:

In some cases, the dependencies that the operator brings with it are not compatible or not desirable with applications that would like to import lws api and client-go library only

See https://go.dev/doc/modules/managing-source

[kerthcet]

We did like this https://github.com/InftyAI/llmaz/blob/5f2f90224d9f4e4d6f5946923acbe6c74f02a340/pkg/controller/inference/service_controller.go#L129-L144, what do you want finally, simplified code structure?

[ahg-g]

One customer reported that they have an old controller-runtime dependency, and when they try to import lws, it causes conflicts. My assumption is that if we put sigs.k8s.io/lws/api/leaderworkerset/v1 and sigs.k8s.io/lws/client-go/applyconfiguration/leaderworkerset/v1 in a separate module, then that would resolve the conflict, wdyt?