Add a possibility to use existing Webhook for Audit instead embedded on install

### Your current KubeKey version

kk version: &version.Info{Major:"3", Minor:"0", GitVersion:"v3.0.10", GitCommit:"3e381c6d5556117d132326b58c5177e0b0e839b6", GitTreeState:"clean", BuildDate:"2023-07-28T06:08:59Z", GoVersion:"go1.19.2", Compiler:"gc", Platform:"linux/amd64"}

### Describe this feature

We can have a possibility to enable the kubernetes auditing using the webook inside of apiserver and so on like https://www.kubesphere.io/docs/v3.4/toolbox/auditing/auditing-receive-customize/

But it works just if the team enter in the server and run kubectl but in kubesphere is not possible to audit it if we not enable the auditing to true inside of clusterconfiguration or via YAML. Enabling the auditing we need deploy many application like opensearch, webhook and sometimes we not have enough resources.

### Describe the solution you'd like

It is possible enable the auditing from Kubesphere to existing webhook instead use the Kubesphere Audit Embedded? It will be great and we can centralize it for the logs coming from kubectl and kubesphere.

As example, I have a existing webhook like http://mywebhoob.net/k8s-audit and I would to use some configuration in kubesphere to send all logs to their webhook

### Additional information

_No response_

No file or test is named. Start by tracing KubeKey's existing embedded audit configuration and the clusterconfiguration/YAML path; determine where an external webhook could be configured. Done means auditing can send Kubernetes and KubeSphere audit logs to an existing webhook without requiring the embedded audit stack.

Written by the indexing model from the issue text.