[rule based autotagging] Add Update Rule API Logic

[ruai0511]

Description

This PR introduces the update Rule API Logic.

An exampe API request is:

curl -XPUT "localhost:9200/_wlm/rule/{rule_id}" -H 'Content-Type: application/json' -d '    
{
    "description": "description",
     "index_pattern": ["log*", "event*"],
     "query_group": "dev_query_group_id_2"
}'

And the return would be

{
    "id":"CtbfXZUBl5pUFqUjPirs",
    "description":"description",
    "index_pattern":["log*","event*"],
    "query_group":"dev_query_group_id_2",
    "updated_at":"2025-03-03T21:17:46.271Z"
}

Rule Schema PR:
#17238
RFC:
#16797

Check List

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

[github-actions]

❌ Gradle check result for 9aa6685: 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 c83500d: 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?

[kaushalmahi12]

Left some high level comments. You can try to review these comments for other API PRs as well to avoid duplicated effort given there is lot of shared code here

[github-actions]

❌ Gradle check result for 3de620c: 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]

@ruai0511 - Gradle failures are related to these code changes. Can you address those?

[Test Result](https://build.ci.opensearch.org/job/gradle-check/58995/testReport/) (4 failures / +4)

    [org.opensearch.rule.rest.RestDeleteRuleActionTests.testRoutes](https://build.ci.opensearch.org/job/gradle-check/58995/testReport/junit/org.opensearch.rule.rest/RestDeleteRuleActionTests/testRoutes/)
    [org.opensearch.rule.rest.RestGetRuleActionTests.testRoutes](https://build.ci.opensearch.org/job/gradle-check/58995/testReport/junit/org.opensearch.rule.rest/RestGetRuleActionTests/testRoutes/)

Also comments have to be resolved, before PR can be merged

[github-actions]

❌ Gradle check result for 13d7147: 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 e4a4e88: 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 84d43f0: 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?

[ruai0511]

flaky test failed. Retrying

[github-actions]

✅ Gradle check result for 4fea47c: SUCCESS

[codecov]

Codecov Report

Attention: Patch coverage is 50.26455% with 94 lines in your changes missing coverage. Please review.

Project coverage is 72.67%. Comparing base (6ad6f4e) to head (4fea47c).
Report is 17 commits behind head on main.

Files with missing lines	Patch %	Lines
...nsearch/rule/action/TransportUpdateRuleAction.java	0.00%	29 Missing ⚠️
...ule/service/IndexStoredRulePersistenceService.java	42.42%	18 Missing and 1 partial ⚠️
...ugin/wlm/rule/WorkloadGroupRuleRoutingService.java	0.00%	15 Missing ⚠️
...org/opensearch/rule/rest/RestUpdateRuleAction.java	21.42%	11 Missing ⚠️
...org/opensearch/rule/autotagging/RuleValidator.java	45.45%	2 Missing and 4 partials ⚠️
...ain/java/org/opensearch/rule/autotagging/Rule.java	44.44%	5 Missing ⚠️
...n/src/main/java/org/opensearch/rule/RuleUtils.java	78.57%	0 Missing and 3 partials ⚠️
...va/org/opensearch/rule/rest/RestGetRuleAction.java	25.00%	3 Missing ⚠️
...org/opensearch/rule/rest/RestDeleteRuleAction.java	33.33%	2 Missing ⚠️
...org/opensearch/rule/rest/RestCreateRuleAction.java	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##               main   #17797    +/-   ##
==========================================
  Coverage     72.66%   72.67%            
- Complexity    67858    67974   +116     
==========================================
  Files          5521     5526     +5     
  Lines        312541   312676   +135     
  Branches      45364    45373     +9     
==========================================
+ Hits         227113   227227   +114     
- Misses        66903    66992    +89     
+ Partials      18525    18457    -68     

☔ 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-17797-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d0c2e39ae05454775b8063e09a88dd5f5834c49f
# Push it to GitHub
git push --set-upstream origin backport/backport-17797-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-17797-to-2.x.