fix otel trace handler WithTracing, use another func

[KubeKyrie]

What type of PR is this?
/kind bug

What this PR does / why we need it:

Fixed OTEL trace interruption when other services requested clusterpedia apiserver. And this is caused by otelhttp.WithPublicEndpoint(). As shown here https://github.com/kubernetes/kubernetes/blob/09a5049ca785024edd4955eb82e855d9b5657491/staging/src/k8s.io/apiserver/pkg/endpoints/filters/traces.go#L33C20-L33C20

And I think it's a bug of kubernetes, so I replaced it with WithTracing in pkg k8s.io/component-base/tracing.

Which issue(s) this PR fixes:
Fixes #None

Special notes for your reviewer:

The two WithTracing is almost same and we can customize the span name by the new one. So it's more flexible.

Does this PR introduce a user-facing change?:

fix otel trace handler WithTracing

[clusterpedia-bot]

Hi @KubeKyrie,
Thanks for your pull request!
If the PR is ready, use the /auto-cc command to assign Reviewer to Review.
We will review it shortly.

Details

Instructions for interacting with me using comments are available here.
If you have questions or suggestions related to my behavior, please file an issue against the gh-ci-bot repository.

[KubeKyrie]

The otelhttp.WithPublicEndpoint() option causes spans generated by the API Server handler to be the start of a new trace (with a link to the incoming trace), rather than be children of the incoming request.
The reason why kube-apiserver uses WithPublicEndpoint is to prevent callers from influencing sampling decisions, see detail kubernetes/kubernetes#109829. And the discussion about the reentrant problem is still in progress, see kubernetes/kubernetes#103186.

So, I think the current solution is to use another handler filter func, just as this PR shows.

[Iceber]

LGTM