[Bug] setting dubbo.application.metadata-type at config center does not take effect

[zrlw]

Pre-check

• I am sure that all the content I provide is in English.

Search before asking

• I had searched in the issues and found no similar issues.

Apache Dubbo Component

Java SDK (apache/dubbo)

Dubbo Version

3.2.12

Steps to reproduce this issue

we want to change metdata store type of all our appliations to remote by setting dubbo.application.metadata-type(kebab-case) or dubbo.application.metadata_type(snake_case) at dubbo.properties on the config center (for mitigating the problems trigged by #14200).
but ConfigurationUtils#parseProperties will drop it because this property name just contains the string value type which is on the securityKey list.

What you expected to happen

setting metadataType by snake_case or kebab-case format on config center should not be prohibited.
or
checking property name is secure or not should not using contains judgement.

Anything else

No response

Are you willing to submit a pull request to fix on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[zrlw]

AbstractConfiguratorListener#genConfiguratorsFromRawRule remove security parameters by calling URLParam#removeParameters which used Map.containsKey:

if (EXTRA_PARAMS.containsKey(key)) {  // the type of EXTRA_PARAMS is map.
   ...
   newExtraParams.remove(key);

should ConfigurationUtils do the same thing?
@AlbumenJ

[zrlw]

ConfigurationUtils#parseProperties might judge whether property name is safe based on kebab-case comparison.