Add Headers as Attributes for Otel traces

[panizzag]

GUS Associated: W-12558102

This commit adds the possibility that the headers processed by the HTTP listener and by the HTTP requester are added as attributes of the spans initialized during the Otel implementation. This new feature takes into account the option of omitting headers that you do not want to register by using a property that is configured at the config element level of both components. An example of use is as follows:

• HTTP Listener

<http:listener-config name="HTTP_Listener_config" doc:name="HTTP Listener config" doc:id="f83efe45-479a-498f-adc1-8848f33ed380" skipHeadersOnTracing="client_id, client_secret">

• HTTP Requester

<http:request-config name="HTTP_Request_configuration" doc:name="HTTP Request configuration" doc:id="3a18fe34-e53b-4ca4-80e2-229cb386f1bb" preserveHeadersCase="true" skipHeadersOnTracing="client_id, client_secret">

• Example cUrl request
  curl --location --request GET 'localhost:8081/test' \ --header 'X-Example-Header: Test' \ --header 'client_id: thisIsAnExampleClientID' \ --header 'client_secret: thisIsAnExampleClientSecret'

The final result is the following:

• Before the change - Attributes registered for the example call

  • Listener:
  
  • Requester:
  

• After the change - Attributes registered for the example call

  • Listener
    

  • Requester
    

[fsgonz]

I would remove the comment for the feature.

[panizzag]

Done. Should I remove all the other similar comments?

[fsgonz]

Thanks very much for the PR, @panizzag!
I have added some cosmetic request for changes for the moment (just in case you have time to add them)
Can you verify if you some unit tests for that. We will be working on adding some integration tests.
Probably we will have to discuss a little bit the new feature with the team but it clear and straightforward.

[panizzag]

Thanks, @fsgonz for the review and suggestions. I have expanded the existing test case to include the new features. I'd appreciate it if the team can give it a new look as there might be coding guidelines and styles that I'm not used to. Thanks

[fsgonz]

Thanks very much. We'll also have to verify if we follow the semantics conventions
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md#http-request-and-response-headers
And if it is enabled by default. Thanks again