Can you set ConfigValidationUtils.MAX_LEGTH longer

Exception in thread "thread-finconfig-firstLoad-pool-0" java.lang.IllegalStateException: Invalid file="-authorityFilter,-catconsumerfilter,-catproviderfilter,-dashboardFilter,-fintech_monitor,-fqtracerconsumer,-fqtracerprovider,-frameworkAttachmentCleConfigValidationUtilsanFilter,-ft_monitor,-ft_tracer_consumer,-ft_tracer_provider,-grpcFilter,-healthcheckfilter,-hystrixconsumerfilter,-ratelimiterfilter,-serviceinfofilter,-strace_log_monitor,-tr_monitor,-tracecontextfilter,-ucsProviderFilter" is longer than 200
at org.apache.dubbo.config.utils.ConfigValidationUtils.checkProperty(ConfigValidationUtils.java:583)
at org.apache.dubbo.config.utils.ConfigValidationUtils.checkMultiName(ConfigValidationUtils.java:558)
at org.apache.dubbo.config.utils.ConfigValidationUtils.checkMultiExtension(ConfigValidationUtils.java:520)
at org.apache.dubbo.config.utils.ConfigValidationUtils.validateAbstractInterfaceConfig(ConfigValidationUtils.java:298)
at org.apache.dubbo.config.utils.ConfigValidationUtils.validateReferenceConfig(ConfigValidationUtils.java:344)
at org.apache.dubbo.config.ReferenceConfig.checkAndUpdateSubConfigs(ReferenceConfig.java:420)
at org.apache.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:193)
at org.apache.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:158)

Start in ConfigValidationUtils.java at checkProperty and the MAX_LEGTH validation reached through checkMultiName and checkMultiExtension. Determine an appropriate longer limit from the reported configuration, then verify that the configuration no longer raises the reported exception and add or update coverage if the repository provides a relevant test.

Written by the indexing model from the issue text.