[v2] Add logging to read/write spans in e2e tests

[james-ryans]

Which problem is this PR solving?

• Helps to debug unstable e2e tests in jaeger-v2 e22 tests are unstable #5418
• Current logs are still hard to follow even it already dump storage's docker and OTEL col binary logs because we can't see which part of the test related to which storage docker/ OTEL col binary logs.

Description of the changes

• Add more logging to e2e tests that capture the timestamp of each read/write run.

How was this change tested?

• Run STORAGE=grpc SPAN_STORAGE_TYPE=memory make jaeger-v2-storage-integration-test

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 95.48%. Comparing base (7df05d9) to head (68ee0a6).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5456      +/-   ##
==========================================
+ Coverage   95.46%   95.48%   +0.01%     
==========================================
  Files         331      331              
  Lines       16112    16112              
==========================================
+ Hits        15382    15384       +2     
+ Misses        556      555       -1     
+ Partials      174      173       -1     

Flag	Coverage Δ
badger_v1	8.08% <ø> (ø)
badger_v2	1.94% <ø> (?)
cassandra-3.x-v1	16.48% <ø> (ø)
cassandra-3.x-v2	1.86% <ø> (ø)
cassandra-4.x-v1	16.48% <ø> (ø)
cassandra-4.x-v2	1.86% <ø> (ø)
elasticsearch-7.x	1.78% <ø> (+0.01%)	⬆️
elasticsearch-8.x	1.77% <ø> (-0.02%)	⬇️
grpc_v1	9.11% <ø> (ø)
grpc_v2	7.49% <ø> (ø)
kafka	9.81% <ø> (ø)
opensearch-1.x	1.78% <ø> (+0.01%)	⬆️
opensearch-2.x	1.78% <ø> (+0.01%)	⬆️
unittests	93.99% <ø> (+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.