[APPENG-927] Yield MetricFilter's as Beans for Spring to apply to MeterRegistry via post processing

[jordanhasgul]

Context

A PR to micrometer (micrometer-metrics/micrometer#4917) added a log message to warn that MeterFilter's have been applied to MeterRegistry after meters have been registered with it.

This library is an offender. This PR no longer explicitly applied MeterFilter's itself and insteads yields them as Beans for Spring to pass to MeterRegistryPostProcessor which will apply them.

Checklist

• Change meets or does not compromise the Baseline Security Requirements

Details from ticket: APPENG-927

Stop explicitly applying MeterFilter's in all platform libraries

Context in Slack thread: [https://wise.slack.com/archives/C0437QJBY4V/p1722955739049859|https://wise.slack.com/archives/C0437QJBY4V/p1722955739049859|smart-link]

We should go over our platform libraries and ensure that we don’t explicitly apply MeterFilter’s to MeterRegistry. Instead we should created the MeterFilter’s and expose them to Spring as Bean’s so that {{MeterRegistryPostProcessor}} can apply them correctly for us.

Known offenders are:

• tw-entrypoints
• tw-service-comms
• tw-tkms
• wise-kafka-processor