Fix instrumentation failure when constructor has @WithSpan annotation

[laurit]

Resolves #13920
This PR excludes constructors from @WithSpan instrumentation since it currently does not work at all. This is not ideal as @WithSpan annotation is allowed on constructors, I don't think we can change that.
Implementing @WithSpan support for constructors is slightly problematic because as far as I can tell on constructors byte buddy does not allow OnMethodExit with onThrowable.

[JonasKunz]

Related bytebuddy issue:
raphw/byte-buddy#375

If we would still want to support tracing constructors with the limitation of exceptions not being detected we could simply create a separate WithSpanConstructorAdvice which omits the onThrowable.

[trask]

Related bytebuddy issue: raphw/byte-buddy#375

If we would still want to support tracing constructors with the limitation of exceptions not being detected we could simply create a separate WithSpanConstructorAdvice which omits the onThrowable.

I think I'd prefer the consistency of never capture constructor calls vs only capture successful constructor calls

@WithSpan annotation is allowed on constructors, I don't think we can change that

if we change that in 3.0, I'm guessing it would only be a "compile-time" breaking change (and wouldn't break any already compiled classes using the annotation)?

[laurit]

if we change that in 3.0, I'm guessing it would only be a "compile-time" breaking change (and wouldn't break any already compiled classes using the annotation)?

I believe so, but have not attempted to verify this.