[Metricbeat][Elasticsearch][ingest_pipeline] In x-pack mode, data is sent to the wrong target

When running in x-pack mode, it is expected that all data from the Elasticsearch module should land in the `.monitoring-*` data stream, but the `ingest_pipeline` metricset doesn't [override](https://github.com/elastic/beats/blob/main/metricbeat/module/elasticsearch/cluster_stats/data.go#L318-L323) the target data stream before the events are shipped, leading them to land in `metricbeat-*`.

Fixing this issue in the Beats code is trivial, but it will also require us to update the Elasticsearch Ingest Pipeline [dashboard](https://github.com/elastic/integrations/blob/main/packages/elasticsearch/kibana/dashboard/elasticsearch-metrics-ingest-pipelines.json) found in the Elasticsearch integration.

Start at metricbeat/module/elasticsearch/cluster_stats/data.go lines 318-323 to trace how the ingest_pipeline metricset selects its target in x-pack mode. Then inspect integrations/packages/elasticsearch/kibana/dashboard/elasticsearch-metrics-ingest-pipelines.json; done means the metricset data lands in the .monitoring-* data stream and the dashboard reflects that target.

Written by the indexing model from the issue text.