Setup body wrapper in otelmux

[martinyonatann]

setup and implementation of a body wrapper in the go.opentelemetry.io/contrib/instrumentation/github.com/gorilla/mux/otelmux package

This PR addresses feedback provided in #6648

[codecov]

Codecov Report

Attention: Patch coverage is 92.30769% with 9 lines in your changes missing coverage. Please review.

Project coverage is 68.8%. Comparing base (9a53a30) to head (ac6d68a).
Report is 4 commits behind head on main.

Files with missing lines	Patch %	Lines
...trumentation/github.com/gorilla/mux/otelmux/mux.go	76.6%	5 Missing and 2 partials ⚠️
...rilla/mux/otelmux/internal/request/body_wrapper.go	93.7%	2 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #6650     +/-   ##
=======================================
+ Coverage   68.7%   68.8%   +0.1%     
=======================================
  Files        200     202      +2     
  Lines      16872   16968     +96     
=======================================
+ Hits       11601   11690     +89     
- Misses      4927    4933      +6     
- Partials     344     345      +1     

Files with missing lines	Coverage Δ
...ux/otelmux/internal/request/resp_writer_wrapper.go	100.0% <100.0%> (ø)
...rilla/mux/otelmux/internal/request/body_wrapper.go	93.7% <93.7%> (ø)
...trumentation/github.com/gorilla/mux/otelmux/mux.go	85.0% <76.6%> (-4.3%)	⬇️

... and 6 files with indirect coverage changes

[akats7]

Does this still apply, since the way you wrap the default writer preserves the original implemented interfaces. Why would you want to implement them in RespWriterWrapper directly.

[dmathieu]

Note that this package is a copy from the otelhttp one.
https://github.com/open-telemetry/opentelemetry-go-contrib/tree/main/instrumentation/net/http/otelhttp/internal/request

Which makes me think maybe it should be templatized instead, to ensure things remain in sync.