Use Helidon tracer, span builder, span types instead of OTel ones so we can trigger span listeners

[tjquinno]

Description

Resolves #8774
Resolves #8370

The Helidon MP telemetry handling of the @WithSpan annotation used the OTel types (tracer, span, and span builder). This made sense initially because @WithSpan is an OpenTelemetry annotation.

Similarly, our container and client filters for setting the correct span context used the OTel types.

But recently we added support for span listeners, and the listeners are invoked from the Helidon wrappers around the various tracing implementations. Because the code that handled @WithSpan and the two filters all used the OTel types directly instead of the Helidon wrappers the listeners were not invoked for spans created due to @WithSpan or the filters.

The main changes in this PR:

• WithSpanInterceptor now uses the Helidon tracing types.
• HelidonTelemetryContainerFilter and HelidonTelemetryClientFilter now use the Helidon tracing types. As part of this change, the filters add the Helidon types to the request contexts so the backside filter method (invoked after the request has been processed) can obtain them and work with them. ([4.x] Should MP OpenTelemetry support add Helidon span, span context, and scope instances to request context? #8370)

Testing changes:

• Addition of a new test to make sure that listeners are invoked for spans triggered by @WithSpan.
• Addition of a new test to make sure that the parent span is set automatically when there is a current one and that the OTel SpanBuilder#setNoParent method works as a way to create a root span.

Documentation

This is a bug fix and has no doc impact.