remove ml config index creation from cron job

[jngz-es]

Description

Related Issues

#3806

Check List

• New functionality includes testing.
• New functionality has been documented.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.97%. Comparing base (ade09e6) to head (fdfd1fa).
Report is 1 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #3850      +/-   ##
============================================
- Coverage     78.02%   77.97%   -0.05%     
- Complexity     7338     7382      +44     
============================================
  Files           656      658       +2     
  Lines         33074    33247     +173     
  Branches       3708     3747      +39     
============================================
+ Hits          25806    25926     +120     
- Misses         5681     5717      +36     
- Partials       1587     1604      +17     

Flag	Coverage Δ
ml-commons	77.97% <ø> (-0.05%)	⬇️

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.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ylwu-amzn]

Rebase with main branch ?

[jngz-es]

Rebase with main branch ?

done

[dhrubo-os]

I have some concerns about removing the ML config index creation from the cron job without having benchmark data on connector initialization times (which includes index creation requests, saving connector information, and key fetching). Having this data would help us better understand the potential impacts and make a more informed decision. Would it be possible to gather this information first?

Specially when we have a static timeout, if we can make it listener based, then I don't have concern with this change.