Dubbo 3.0 在k8s中的服务发现 （一个思考可能放在issue里面不太合适，但是不知道放在哪里）

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

### Environment

* Dubbo version: 3.0.0
* Operating System version: xxx
* Java version: xxx

### Steps to reproduce this issue
目前在k8s中的服务发现解决方案有二个
1、 DNS ，无头服务，对dns会有一定的查询压力
2、k8s client, 当 consumer 过多时会对api server 有压力，配置失误可能会拖垮k8s集群

我觉得可以换一个思路，让 provider 做服务发现
具体步骤是这样的
1、provider 服务采用普通服务
2、provider 负责监听 k8s endpoints变化
3、consumer 使用 k8s中创建 provider 的普通服务做服务发现

这样一来 consumer 端 可以把查询dns 转成向provider查询，减少dns的查询压力，同时provider只需要身k8s监听自己服务的变化通知，减少配置失误对k8s集群的影响

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

### Expected Result

What do you expected from the above steps？

### Actual Result

What actually happens?

If there is an exception, please attach the exception trace:

```
Just put your stack trace here!
```

The issue names no files, tests, or entry points. Start by reviewing Dubbo 3.0's existing Kubernetes service-discovery options and the provider/consumer flow described here; done would require a decided, scoped proposal with validation criteria.

Written by the indexing model from the issue text.