[Rule based auto tagging] Add in-memory rule processing service

[kaushalmahi12]

Description

This change adds the service class for managing in-memory view of rules and evaluates the target label for incoming search requests.

Do not review the following files since they are part of other PRs

• Rule.java PR
• build.gradle, Everything under storage package and corresponding UTs PR

Related Issues

#16797 (comment)

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

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.

[github-actions]

❌ Gradle check result for 09e3013: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 3bea59a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[jainankitk]

@kaushalmahi12 - Precommit failing due to license error:

Execution failed for task ':plugins:workload-management:dependencyLicenses'.
> Licences dir /home/runner/work/OpenSearch/OpenSearch/plugins/workload-management/licenses does not exist, but there are dependencies: commons-collections4-4.4.jar

[sgup432]

LGTM overall

[github-actions]

❌ Gradle check result for e502a38:

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[jainankitk]

Thanks @kaushalmahi12 for this PR. Mostly looks good, have few minor comments

[github-actions]

❌ Gradle check result for cfeaace: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 512b0ca: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

✅ Gradle check result for 8a9aeb8: SUCCESS

[codecov]

Codecov Report

Attention: Patch coverage is 87.32394% with 9 lines in your changes missing coverage. Please review.

Project coverage is 72.39%. Comparing base (15d27a1) to head (8a9aeb8).
Report is 7 commits behind head on main.

Files with missing lines	Patch %	Lines
...wlm/rule/attribute_extractor/IndicesExtractor.java	0.00%	5 Missing ⚠️
...opensearch/rule/InMemoryRuleProcessingService.java	94.87%	0 Missing and 2 partials ⚠️
...earch/rule/storage/AttributeValueStoreFactory.java	83.33%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #17365      +/-   ##
============================================
- Coverage     72.43%   72.39%   -0.05%     
+ Complexity    66065    66027      -38     
============================================
  Files          5351     5355       +4     
  Lines        306220   306338     +118     
  Branches      44376    44386      +10     
============================================
- Hits         221812   221759      -53     
- Misses        66272    66445     +173     
+ Partials      18136    18134       -2     

☔ 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.

[opensearch-trigger-bot]

The backport to 2.x failed:

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

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-17365-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8312e42362e3fdb068cbe6b36edaeabc2f987f47
# Push it to GitHub
git push --set-upstream origin backport/backport-17365-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x

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