Cherry-pick #16971 to 7.x: Make use of prometheus filter settings on IBM-MQ Metricbeat module

[ChrsMark]

Cherry-pick of PR #16971 to 7.x branch. Original message:

What does this PR do?

Refactoring the manifest file of the qmgr metricset. Previously a processor was used to filter out non ibmmq metrics. This commit replaces the processor with the more elegant metrics_filter that was introduced recently.

Why is it important?

Using the metrics_filter is cleaner and easier to read.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• [ ] I have added tests that prove my fix is effective or that my feature works

How to test this PR locally

• Run the IBM MQ container ("docker-compose up" in x-pack/metricbeat/module/ibmmq) locally.
• Run metricbeats with the ibmmq module enabled.
• In Kibana look at the imported metric data -> For metricset qmgr, you should see only metrics beginning with "prometheus.metrics.ibmmq_qmgr"
• Remove the metrics_filter from the manifest file and restart metricbeats
• In Kibana look at the imported metric data -> For metricset qmgr, you should see a number of metrics not beginning with "prometheus.metrics.ibmmq_qmgr" besides metrics beginning with that prefix.

[mtojek]

Thanks for fixing this!