Fix memory increase caused by go tracer

Bug: A gradual memory increase was noticed after tracing release.

This bug was caused by a go routine running in golang microservices via consul loop or apigatewayReceiver consul loop. The go routine which was polling consul for every 5min was also creating 2-3 more go routines which were never getting destroyed. These new go routines were part of the otel library caused by trace.NewTracerProvider function call.

The solution was to simply call the function only once in the entire application lifecycle.

What's Changed

• debug and fix memory increase in gotracer by @cw-balaji in #213

Full Changelog: v1.13.2...v1.13.3