Move the cluster_id processor to the Beats repository

[ofiriro3]

Motivation As mentioned by several developers, the cluster_id processor that we introduced in Cloudbeat, could be relevant for other beats.

In-depth Lately, we have extended the add_cluster_id processor, to support adding the cluster name, and we suspect that in the future we would like to extend it even more to add all sort of orchestrator fields.

When implementing the solution, one should consider the following:

1. The code should be backward and forward-compatible with the integration since the integration can introduce and old integration with a new agent and the opposite way around.

Definition of done

• Move the processor to Beats
• What happens if someone will enable the add_kubernetes_metadata processor in the beats along with this processor?
• Maybe we should rename this processor.

Related tasks/epics

• https://github.com/elastic/cloudbeat/issues/391
• https://github.com/elastic/beats/issues/33081

[ofiriro3]

cc @ChrsMark @oren-zohar @kfirpeled