dubbo3.0应用级服务发现, 服务端配置payload后, 消费端无法取到

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

## Ask your question here
使用dubbo3.0应用级服务发现的场景下, 消费者调用服务端时报错"Data length too large:xxxxxx, max payload: 8388608"。
断点在ExchangeCodec.finishRespWhenOverPayload.getPayload方法中，无论服务端如何修改配置，channel.getUrl始终没有payload属性。
channel.getUrl：dubbo://10.20.4.17:21868/org.apache.dubbo.metadata.MetadataService?codec=dubbo&connect.lazy.initial.state=true&dubbo=2.0.2&group=xxx-service&heartbeat=60000&port=21868&protocol=dubbo&release=3.0.4&send.reconnect=true&side=consumer&timeout=5000&version=1.0.0

Start at ExchangeCodec.finishRespWhenOverPayload.getPayload and reproduce the application-level service discovery call that reports a payload larger than 8388608. Inspect how the server payload configuration is propagated into channel.getUrl for the MetadataService consumer. Done means the consumer receives the configured payload limit and the failing response is handled without the reported error.

Written by the indexing model from the issue text.