Stabilize HTTP library instrumentation

[trask]

Tracking issue

• Remove experimental methods out of (to-be-public) TelemetryBuilder classes #12847
• Rename ktor tracing to ktor telemetry #12855
• Move AbstractKtorClientTracing (and everthing under ktor-2-common) under *.v2_0.common package (currently it has no version in the package) Rename ktor tracing to ktor telemetry #12855
• Rename ApacheHttpClient5Telemetry to ApacheHttpClientTelemetry (since already under v5 package) #12854
• Consistency between setKnownMethods(Set<String>), setCapturedRequestHeaders(List<String>) and setCapturedResponseHeaders(List<String>) #12848
• Split unified http client/server telemetry builders into separate telemetry builders (one for client and one for server)
  • ArmeriaTelemetryBuilder Split ArmeriaTelemetry into client and server #12851
  • RatpackTelemetryBuilder Split ratpack into client and server #12853
  • SpringWebfluxTelemetryBuilder Split Webflux into client and server #12852
• Ensure consistent API across all Telemetry and TelemetryBuilder classes
  • Consistent naming of addAttributesExtractor #12860
  • Simplify Http *TelemetryBuilder generic signatures #12858
• Consider not using framework classes as request and response as this may limit possibilities for evolving the instrumentations without breaking changes
• Better qualify Java HttpClient instrumentation package name #13296

Any breaking changes should be done across two separate releases

1. Introduce the new method/class and deprecate the old method/class
2. Remove the deprecated method/class