Added a docker-compose for hotrod e2e test

[hellspawn679]

Which problem is this PR solving?

• Enhance e2e test for HotROD #5735

Description of the changes

• added docker-compose file to test hotrod so that is can connect to jaeger

How was this change tested?

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: yarn lint and yarn test

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.66%. Comparing base (c68136e) to head (9d82e79).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5740   +/-   ##
=======================================
  Coverage   96.66%   96.66%           
=======================================
  Files         341      341           
  Lines       16451    16451           
=======================================
  Hits        15902    15902           
  Misses        361      361           
  Partials      188      188           

Flag	Coverage Δ
badger_v1	8.05% <ø> (ø)
badger_v2	1.90% <ø> (ø)
cassandra-3.x-v1	16.61% <ø> (ø)
cassandra-3.x-v2	1.82% <ø> (ø)
cassandra-4.x-v1	16.61% <ø> (ø)
cassandra-4.x-v2	1.82% <ø> (ø)
elasticsearch-6.x-v1	18.77% <ø> (-0.02%)	⬇️
elasticsearch-7.x-v1	18.83% <ø> (ø)
elasticsearch-8.x-v1	19.03% <ø> (ø)
elasticsearch-8.x-v2	1.90% <ø> (+0.01%)	⬆️
grpc_v1	9.52% <ø> (ø)
grpc_v2	7.47% <ø> (ø)
kafka	9.74% <ø> (ø)
memory_v2	1.90% <ø> (ø)
opensearch-1.x-v1	18.89% <ø> (ø)
opensearch-2.x-v1	18.88% <ø> (-0.02%)	⬇️
opensearch-2.x-v2	1.90% <ø> (+0.01%)	⬆️
unittests	95.08% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[yurishkuro]

I suggest you explain your plan, doesn't seem it's going in the right direction. We already have all the pieces you included in this PR

[hellspawn679]

@yurishkuro my plan is to build a local hotrod image(localhost:5000/jaegertracing/example-hotrod:${GITHUB_SHA:-latest}) and test it using docker-compose(that way we won't have any error for port 4318) then we will hit the frontend end point and get the hotrod logs and get the tracesID from there

[yurishkuro]

you have UI submodule affected in this PR, please remove.

[yurishkuro]

lgtm, a couple open questions

[yurishkuro]

Thanks!

[yurishkuro]

this line should not have been deleted. It needs to run as the last step of the script.