Spans around Methods with Include: Capture Method Input Param as Span Attributes

[zoomingrocket]

Is your feature request related to a problem? Please describe.
We are using (Spans Around Methods with Include) feature to create spans around methods within COTS system for which no traditional instrumentation is available. Everything works out really well except all the spans are named with Class.Method by default does not help in meaningful analysis or debugging of problem areas.

Describe the solution you'd like
Request to enhance the spans around methods to capture all method input parameters as attributes. This will help us use span processors to rename spans appropriately as desired use case by use case

E.g. If the span around method is enabled for Class.Method and Method takes 5 input params, make all 5 input params available as span attributes inp1=value1;inp2=value2;inp3=value3;inp4=value4;inp5=value5 and so on

Describe alternatives you've considered
We have captured the verbose log for such spans and noticed that we do not have any attributes captured today, so no meaningful data is available to rename spans.
Since we are using COTS middleware systems we have limited scope of changing existing Java code and only the request entry class is custom this feature is a huge saver to create spans properly as the rest of the dependencies are already properly captured with standard instrumentation for APIs, database, JMS, etc. So being able to rename spans properly will be a huge help.

[trask]

This is probably unblocked now if anyone wants to work on it by the availability now of (experimental) yaml-based configuration