Fix possible memory leak in ObjectNameAttributeFilter

[kw4s]

If:

• autoExcludeObjectNameAttributes is set to true (and it is by default)
• application registers and unregisters a lot of MBeans with unique names
• those MBeans contain attribute types that cannot be exported

Then the ObjectNameAttributeFilter will cause a memory leak where excludeObjectNameAttributesMap will keep adding information about new beans to the exclude map but will never remove it, keeping information about beans no longer registered in MBeanServer:

I've added similar approach to what is already implemented in JmxMBeanPropertyCache - that is, once we get a new list of beans that we're interested in, remove any old ones from the cache and dynamic attribute filter.
I've also split excludeObjectNameAttributesMap into two maps, one for attributes from config (as we don't want to remove them automatically) and the other one for dynamically added attributes (those should be considered for removal).
This approach will also be relevant when resolving conflicts with #897 (as there the property names from config should be treated as patterns but property names added dynamically should be treated as "literal" - compared with equals).

[kw4s]

the minimal reproducible example (after adding necessary imports): https://gist.github.com/kw4s/8b4b3f9e076bec01f2a29f3651ce1d06

[dhoard]

@kw4s thanks for the PR!!!

Can you sign your PR (DCO requirement)?

Have you ran the integration tests?

[kw4s]

@dhoard
Hi, I've amended the commit to add sign-off, I've also applied spotless required changes (did not run full build before, and I did not notice there is style enforced, sorry about that) and checked all integration tests, all PASS.