Add ability to filter out metric by id name

[ibilley7]

Users might want to the ability to filter out metrics that are not necessary for them to view. Created a static getMeterFilter function in MeterRegistryFactory to filter out metrics user does not want to see. Created new Property GENERAL_MICROMETER_ID_FILTERS, and filters specified via this property will be added to meter registries created in MeterInfoImpl

Closes issue #4599

[lbschanno]

This PR is failing checks because we need to specifically allow the MeterFilter class within the apilyzer configuration. You need to insert the following:

<allow>io[.]micrometer[.]core[.]instrument[.]config[.]MeterFilter</allow>

to core/pom.xml, directly below where there is a similar statement for MeterRegistry, line 301, so that we then have the following:

 <allows>
                <allow>io[.]micrometer[.]core[.]instrument[.]MeterRegistry</allow>
                <allow>io[.]micrometer[.]core[.]instrument[.]config[.]MeterFilter</allow>
                <allow>io[.]opentelemetry[.]api[.]OpenTelemetry</allow>
                ...

[DomGarguilo]

This looks pretty good. I am wondering if we should switch the filtering from a "deny list" to an "accept list" i.e. instead of defining which meters we want to filter out, we define a filter for only the meters we want to see. I don't think it makes a huge difference but might make things more intuitive or safer but I'm open to considering others opinions on this.

[DomGarguilo]

I'm wondering if we should allow an empty value here. The default value is currently an empty String anyways. We could just handle an empty string as no filter.

[ibilley7]

Wouldn't passing an empty string through the function defeat the purpose of getMeterFilter?