Introduce Ml Inference Search Request Extension

[mingshl]

Description

Introduce Ml Inference Search Request Extension, this is adding ml_inference search extension during search request/query phase,

For the search response side, I already introduced a ml_inference search response extension in earlier PR released in 2.18. Support ML Inference Search Processor Writing to Search Extension

Related Issues

#3286
#3054

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.

[dhrubo-os]

@mingshl let's take the update from main. File has conflict.

[mingshl]

thanks @dhrubo-os ， rebased and resolved conflicts.

[dhrubo-os]

Tests are failing

[mingshl]

Tests are failing

there is no changes related to ConversationalMemory, will try rerun the tests.

> Task :opensearch-ml-memory:test

ConversationalMemoryHandlerITTests > testDifferentUsers_DifferentConversations FAILED
    java.lang.NoClassDefFoundError at ConversationalMemoryHandlerITTests.java:389
        Caused by: java.lang.ClassNotFoundException at ConversationalMemoryHandlerITTests.java:389

[mingshl]

rebased and resolved conflicts.

[dhrubo-os]

D:\a\ml-commons\ml-commons\common\build\generated\sources\delombok\java\main\org\opensearch\ml\common\utils\StringUtils.java:379: error: unknown tag: implNote
     * @implNote This method uses JsonPath for JSON manipulation and StringUtils for path existence checks.
       ^

[mingshl]

Looks good overall, but can you add REST test cases with some non trivial examples?

I added two REST tests to verify in the new commit add REST test and javadoc and just rebased the changes from main branch

[codecov]

Codecov Report

Attention: Patch coverage is 85.03401% with 22 lines in your changes missing coverage. Please review.

Project coverage is 80.38%. Comparing base (f28bb74) to head (bafd235).
Report is 175 commits behind head on main.

Files with missing lines	Patch %	Lines
...l/processor/MLInferenceSearchRequestProcessor.java	68.00%	5 Missing and 3 partials ⚠️
...ava/org/opensearch/ml/processor/ModelExecutor.java	58.82%	5 Missing and 2 partials ⚠️
...ml/searchext/MLInferenceRequestParametersUtil.java	75.00%	1 Missing and 3 partials ⚠️
...rg/opensearch/ml/plugin/MachineLearningPlugin.java	50.00%	2 Missing ⚠️
...va/org/opensearch/ml/common/utils/StringUtils.java	97.67%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #3284      +/-   ##
============================================
- Coverage     81.31%   80.38%   -0.93%     
- Complexity     6094     6720     +626     
============================================
  Files           573      602      +29     
  Lines         25268    28972    +3704     
  Branches       2666     3213     +547     
============================================
+ Hits          20547    23290    +2743     
- Misses         3601     4307     +706     
- Partials       1120     1375     +255     

Flag	Coverage Δ
ml-commons	80.38% <85.03%> (-0.93%)	⬇️

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.

[dhrubo-os]

I didn't get the time to review the PR thoroughly. But approving the PR not to block. @austintlee could you please review this PR as you know more of this context. Thanks.

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-3284-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 3cbd09ab2c9924c9c81214f0d24c20b2f5b58a02
# Push it to GitHub
git push --set-upstream origin backport/backport-3284-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-3284-to-2.x.

[mingshl]

backport conflict due to this PR also changes in StringUtils, but it merge in main not backport to 2.x yet #3342