Fixed update payload for correlation rule

[amsiglan]

Description

If the query or field properties of correlation rule data source are empty, they should be null or not exist in the payload for the correlation rule to work correctly after update.

Check List

• Commits are signed per the DCO using --signoff

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 ✅

Comparison is base (145fec9) 31.01% compared to head (776a54f) 31.01%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #838      +/-   ##
==========================================
- Coverage   31.01%   31.01%   -0.01%     
==========================================
  Files         151      151              
  Lines        5101     5108       +7     
  Branches      890      946      +56     
==========================================
+ Hits         1582     1584       +2     
- Misses       3329     3334       +5     
  Partials      190      190              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[AWSHurneyt]

Changes LGTM. Approving assuming the tests pass.

[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/security-analytics-dashboards-plugin/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/security-analytics-dashboards-plugin/backport-2.x
# Create a new branch
git switch --create backport-838-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 368adf79568cd8de6884bab5fb5adeee81223152
# Push it to GitHub
git push --set-upstream origin backport-838-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/security-analytics-dashboards-plugin/backport-2.x

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