[jaeger-v2] Align Cassandra Storage Config With OTEL

[mahadzaryab1]

Which problem is this PR solving?

• Resolves [jaeger-v2] Align Cassandra Storage Config With OTEL #5928

Description of the changes

• Revamped configuration for Cassandra to be logically grouped
• Added unit tests for the Validate method
• Changed the configuration to use OTEL's configtls.ClientConfig type
• Migration guide

How was this change tested?

• New unit tests
• CI

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

Attention: Patch coverage is 97.95918% with 2 lines in your changes missing coverage. Please review.

Project coverage is 96.90%. Comparing base (d7f01d1) to head (2f1f0e9).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/cassandra/config/config.go	96.72%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5949      +/-   ##
==========================================
+ Coverage   96.80%   96.90%   +0.10%     
==========================================
  Files         349      349              
  Lines       16581    16582       +1     
==========================================
+ Hits        16051    16069      +18     
+ Misses        342      329      -13     
+ Partials      188      184       -4     

Flag	Coverage Δ
badger_v1	8.00% <0.00%> (-0.01%)	⬇️
badger_v2	1.82% <0.00%> (-0.01%)	⬇️
cassandra-4.x-v1	15.78% <87.75%> (-0.79%)	⬇️
cassandra-4.x-v2	1.75% <0.00%> (-0.01%)	⬇️
cassandra-5.x-v1	15.78% <87.75%> (-0.79%)	⬇️
cassandra-5.x-v2	1.75% <0.00%> (-0.01%)	⬇️
elasticsearch-6.x-v1	18.72% <0.00%> (-0.01%)	⬇️
elasticsearch-7.x-v1	18.78% <0.00%> (-0.01%)	⬇️
elasticsearch-8.x-v1	18.98% <0.00%> (-0.01%)	⬇️
elasticsearch-8.x-v2	1.82% <0.00%> (-0.01%)	⬇️
grpc_v1	9.53% <0.00%> (-0.01%)	⬇️
grpc_v2	7.12% <0.00%> (-0.02%)	⬇️
kafka-v1	9.71% <0.00%> (-0.01%)	⬇️
kafka-v2	1.82% <0.00%> (-0.01%)	⬇️
memory_v2	1.82% <0.00%> (-0.01%)	⬇️
opensearch-1.x-v1	18.84% <0.00%> (-0.01%)	⬇️
opensearch-2.x-v1	18.84% <0.00%> (-0.01%)	⬇️
opensearch-2.x-v2	1.81% <0.00%> (-0.02%)	⬇️
tailsampling-processor	0.46% <0.00%> (-0.01%)	⬇️
unittests	95.70% <95.91%> (+0.41%)	⬆️

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.

[mahadzaryab1]

Is NamespaceConfig still relevant (https://github.com/jaegertracing/jaeger/blob/main/plugin/storage/cassandra/options.go#L70-L74)? Or can we replace it with the Configuration type?

[mahadzaryab1]

@yurishkuro This is ready for another look. The patch code coverage is failing because of a couple of lines which were modified that I'm assuming weren't tested before. Should I add some tests for NewCluster?

[yurishkuro]

Thanks!

[yurishkuro]

migration doc not readable

[mahadzaryab1]

@yurishkuro thank you so much for writing the tests! the linter was failing so I just fixed that. Auto merge was disabled so will need to be enabled or merged in again.

[mahadzaryab1]

migration doc not readable

sorry about that! just opened the access up

[mahadzaryab1]

I think we have a one-off failure for the ES test. I think a rerun of the CI should fix it since we didn't touch anything ES related in this PR.