[WIP][feat]: Support elasticsearch data stream

[zzzk1]

Which problem is this PR solving?

Resolves #4708

Provide follow API to client

• Create ILM Policy
• Create DataStream using exist index template
• Convert index alias with a write index to a DataStream

Description of the changes

• allow ilm_client to create ILM Policy directly

How was this change tested?

• unit test & intergration 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: npm run lint and npm run test

[Manik2708]

@yurishkuro @zzzk1 My question for this PR is: Do we need to support DefaultPolicy through es-rollover? ILM is to automate rollover and back data streams index, when the need is to automate rollover why should we keep it in a script which requires mannual rollover?

[zzzk1]

@yurishkuro @zzzk1 My question for this PR is: Do we need to support DefaultPolicy through es-rollover? ILM is to automate rollover and back data streams index, when the need is to automate rollover why should we keep it in a script which requires mannual rollover?

@Manik2708 Thanks for your remind. Just for testing easily now; once all features are implemented, then migration to cmd/Jaeger will occur.

[codecov]

Codecov Report

Attention: Patch coverage is 87.87879% with 4 lines in your changes missing coverage. Please review.

Project coverage is 96.23%. Comparing base (b04e0ba) to head (56b2b20).

Files with missing lines	Patch %	Lines
pkg/es/client/ilm_client.go	85.00%	2 Missing and 1 partial ⚠️
pkg/es/client/datastream_client.go	92.30%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6551      +/-   ##
==========================================
- Coverage   96.24%   96.23%   -0.02%     
==========================================
  Files         373      374       +1     
  Lines       21406    21439      +33     
==========================================
+ Hits        20602    20631      +29     
- Misses        612      615       +3     
- Partials      192      193       +1     

Flag	Coverage Δ
badger_v1	10.64% <ø> (ø)
badger_v2	2.77% <ø> (ø)
cassandra-4.x-v1-manual	16.58% <ø> (ø)
cassandra-4.x-v2-auto	2.71% <ø> (ø)
cassandra-4.x-v2-manual	2.71% <ø> (ø)
cassandra-5.x-v1-manual	16.58% <ø> (ø)
cassandra-5.x-v2-auto	2.71% <ø> (ø)
cassandra-5.x-v2-manual	2.71% <ø> (ø)
elasticsearch-6.x-v1	20.37% <ø> (ø)
elasticsearch-7.x-v1	20.44% <ø> (ø)
elasticsearch-8.x-v1	20.59% <ø> (ø)
elasticsearch-8.x-v2	2.77% <ø> (-0.11%)	⬇️
grpc_v1	12.16% <ø> (ø)
grpc_v2	9.02% <ø> (ø)
kafka-3.x-v1	10.32% <ø> (ø)
kafka-3.x-v2	2.77% <ø> (ø)
memory_v2	2.77% <ø> (+<0.01%)	⬆️
opensearch-1.x-v1	20.49% <ø> (+<0.01%)	⬆️
opensearch-2.x-v1	20.48% <ø> (-0.01%)	⬇️
opensearch-2.x-v2	2.76% <ø> (-0.01%)	⬇️
tailsampling-processor	0.51% <ø> (ø)
unittests	95.08% <87.87%> (-0.02%)	⬇️

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]

how would our own code know what the policy should look like?

[yurishkuro]

This is a large new feature, please describe how you see everything working before jumping into implementation (which is likely going to be a waste of time if we don't agree on the approach first)

[zzzk1]

This is a large new feature, please describe how you see everything working before jumping into implementation (which is likely going to be a waste of time if we don't agree on the approach first)

Yes, I will submit a descripton doc