Support list-watch from edgecore for applications on the edge

[fisherxu]

Why do we need it

Some applications running on the edge side need to connect to the k8s master through list-watch interface, but on the edge it cannot directly connect to the k8s master. So we need forward the list-watch requests to the k8s master through the cloud-side channel.

[GsssC]

For my view, there are two methods to implement :

1. The first way

• how to handle list request
  

• how to handle watch request
  

Advantage:
- client could list watch all type source from edge.
Disadvantage:
- architecture complex
- no reuse of existing cloud-edge channel

2. The second way , reuse cloud-edge channel

• how to handle list request

• how to handle watch request

Advantage:
- reuse of existing cloud-edge channel
Disadvantage:
- we need add codes from cloudcore to edgecore for supporting proxy a specific type of resource like crd

3. QUESTION

1. do we need to support listwatching all resource on edge?**

[stale]

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).