<!-- If you need to report a security issue please visit https://github.com/apache/dubbo/security/policy -->

- [x] I have searched the [issues](https://github.com/apache/dubbo/issues) of this repository and believe that this is not a duplicate.

### Environment

* Dubbo version: 3.1.11
* Operating System version: MAC
* Java version: 1.8

### Steps to reproduce this issue

1. 使用3.1.11的版本定义一个接口提供服务，接口中包含相同名字不同参数的X个方法，那么在provider的url上methods参数就会有多个重复的方法名
2. 在2.6.x的consumer端引用该服务时，methodInvokerMap会根据相同方法名存放X个重复invoker地址，如果默认使用random负载均衡，相当于该provider有着X倍的权重一样，压力会是X倍
3. 在刚升dubbo3的时候，如果一台机器收到的流量是其他机器的X倍，可能压力较大会有风险

![duplicate](https://github.com/apache/dubbo/assets/3276231/fa4c2aab-e13c-4bd8-8b8a-3bfada07175c)
![addMap](https://github.com/apache/dubbo/assets/3276231/79b59170-020a-482e-82e2-0ebd6e162d67)


Pls. provide [GitHub address] to reproduce this issue.

### Expected Behavior

在生成provider url的methods参数时，去掉重复的方法名

### Actual Behavior

同名不同参数的方法名，会在url上生成多次

红圈中是灰度发布一台的重复现象
![methods](https://github.com/apache/dubbo/assets/3276231/6c27459e-dc1b-4ad8-b1bf-57c51115c4d8)


MetricsEventBus.post(RegistryEvent.toRsEvent(module.getApplicationModel(), getUniqueServiceName(), protocols.size() * registryURLs.size()),
            () -> {
                for (ProtocolConfig protocolConfig : protocols) {
                    String pathKey = URL.buildKey(getContextPath(protocolConfig)
                        .map(p -> p + "/" + path)
                        .orElse(path), group, version);
                    
                    if (!serverService) {
                        
                        repository.registerService(pathKey, interfaceClass);
                    }
                    doExportUrlsFor1Protocol(protocolConfig, registryURLs, register);
                }
                return null;
            }
        );
        providerModel.setServiceUrls(urls);
    }
    private void doExportUrlsFor1Protocol(ProtocolConfig protocolConfig, List<URL> registryURLs, boolean register) {
        Map<String, String> map = buildAttributes(protocolConfig);
        
        map.keySet().removeIf(key -> StringUtils.isEmpty(key) || StringUtils.isEmpty(map.get(key)));
        
        serviceMetadata.getAttachments().putAll(map);
        URL url = buildUrl(protocolConfig, map);
        processServiceExecutor(url);
        exportUrl(url, registryURLs, register);
    }
    private void processServiceExecutor(URL url) {
        if (getExecutor() != null) {