[Feature] Support available layers of service in the topology.

[wu-sheng]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

Topology node includes name and ID. Due to the hierarchy service feature, we have default service dashboard setup, we could consider adding layers(possibly multiple) to the node, and give UI a chance to jump into another layer's dashboard of the service.

@wankai123 Let's discuss the possibility of this, and we will need an official SWIP for this.

Use case

In the typical use cases, <1> mesh and mesh-dp share a similar topology, <2> agent + virtual services(MQ, DB, Cache), both of these two cases have hybrid layer topology.
If we could support that, we could have a better x-layer interaction.

In the above cases, @Fine0830 Node topology widget could support jumping into another layer's dashboard, if the node has different layers than the layer of the current dashboard. The difference means,

• Case <1>, node will have two layers, one is as same as the current dashboard, the other is different.
• Case <2>, some nodes will have a different layer, virtual database layer node exists in the general layer topology.

Related issues

No response

Are you willing to submit a pull request to implement this on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[wu-sheng]

Refer to #11834 for the solution.

[wu-sheng]

We have kernel level support for this now.

Major features of 10.0 are done.

I want to wait for @hanahmily BanyanDB testing. And then @mrproliu could follow #11619

It is better 10.0 have all these.