[jaeger-v2] Extend integration tests for memstore

[akagami-harsh]

Which problem is this PR solving?

• part of [tracking] Jaeger v2 based on OpenTelemetry collector #4843

Description of the changes

• Extended integration tests for memstore used in jaeger-v2

How was this change tested?

• tested locally

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 ✅

Comparison is base (5375e1e) 94.44% compared to head (e61caa3) 94.48%.
Report is 5 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5215      +/-   ##
==========================================
+ Coverage   94.44%   94.48%   +0.03%     
==========================================
  Files         332      334       +2     
  Lines       19189    19254      +65     
==========================================
+ Hits        18124    18192      +68     
+ Misses        878      875       -3     
  Partials      187      187              

Flag	Coverage Δ
cassandra-3.x	28.65% <ø> (+3.07%)	⬆️
cassandra-4.x	28.65% <ø> (+3.07%)	⬆️
elasticsearch-5.x	23.70% <ø> (+3.84%)	⬆️
elasticsearch-6.x	23.70% <ø> (+3.84%)	⬆️
elasticsearch-7.x	23.84% <ø> (+3.84%)	⬆️
elasticsearch-8.x	23.93% <ø> (+3.84%)	⬆️
grpc-badger	20.12% <ø> (+0.63%)	⬆️
kafka	19.63% <ø> (+5.54%)	⬆️
opensearch-1.x	23.84% <ø> (+3.84%)	⬆️
opensearch-2.x	23.84% <ø> (+3.85%)	⬆️
unittests	92.30% <ø> (+0.01%)	⬆️

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]

Sorry, I don't follow what problem this PR is solving. memstore is already tested in in integration tests.