[Bug] Enhance VNode logic and support multiple Trace IDs in span's ref

[wu-sheng]

Search before asking

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

Apache SkyWalking Component

UI (apache/skywalking-booster-ui)

What happened

When I worked with @CzyerChen on apache/skywalking-java#665, I noticed these two

source apache/skywalking-java#665 (comment)

What you expected to happen

There are two things we should enhance

1. If the span has multiple references, and there is at least one segment ID + span ID that could be found as the parent, others should not be shown as a virtual node
2. Case <1> or different trace IDs in the reference exist, then we should list those trace ID in the span page, and support a jump based on Trace ID query.

How to reproduce

Typically process is MQ bulk consuming, such as https://github.com/apache/skywalking-java/pull/665bulk-consuming

Anything else

No response

Are you willing to submit a pull request to fix 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]

@CzyerChen You could try to sync the UI submodule and test this with your MQ bulk consuming. I hope this could resolve VNode for the case, and support to jump into associated traces.

[CzyerChen]

@CzyerChen You could try to sync the UI submodule and test this with your MQ bulk consuming. I hope this could resolve VNode for the case, and support to jump into associated traces.

With the latest frontend code, the view of rocketmq-5-grpc-scenario looks great.