Expose otel configured thrift http port

[albertteoh]

Signed-off-by: albertteoh see.kwang.teoh@gmail.com

Which problem is this PR solving?

• A proposed means of addressing the support question: Unable to collect metrics for SPM #3975

Short description of the changes

• A support question was submitted to provide an example where a Python application's R.E.D metrics can be visualised based just on the spans it emits.
• I had considered creating a new repo that brings up the components required for SPM, but realised it's almost exactly the same as the SPM dev environment in jaeger, just with microsim removed, and most importantly, exposing the port listened on by OTEL's jaeger receiver on port 14278.
• The simpler option is just to expose the above port from within this dev environment, which also opens the opportunity for any other local application to emit spans to, to view their own R.E.D metrics.

Testing

With a custom simple Python script that generates a 3-tiered trace on service my_service and emits them to localhost:14278, the R.E.D metrics are visible in Jaeger SPM:

[codecov]

Codecov Report

Base: 97.15% // Head: 97.16% // Increases project coverage by +0.01% 🎉

Coverage data is based on head (c372522) compared to base (64f9699).
Patch has no changes to coverable lines.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3986      +/-   ##
==========================================
+ Coverage   97.15%   97.16%   +0.01%     
==========================================
  Files         295      295              
  Lines       17389    17389              
==========================================
+ Hits        16894    16896       +2     
+ Misses        399      397       -2     
  Partials       96       96              

Impacted Files	Coverage Δ
...lugin/sampling/strategystore/adaptive/processor.go	100.00% <0.00%> (+0.61%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[yurishkuro]

1. Should there be that many ports exposed from all-in-one? It seems in this setup all collection should go through OTEL collector.
2. May be useful to explain this in the readme.

[albertteoh]

Thanks for the feedback @yurishkuro, good points. I'll address them in a follow-up PR.