Add workflowId field in alert model

[eirsep]

Description

Add workflowId field in alert model.
This field would be populated when alerts are created by monitors executing within a workflow. Else field would be an empty string

[codecov]

Codecov Report

Merging #463 (a508699) into main (f1c0f1d) will decrease coverage by 0.06%.
The diff coverage is 62.50%.

@@             Coverage Diff              @@
##               main     #463      +/-   ##
============================================
- Coverage     73.83%   73.77%   -0.06%     
- Complexity      824      825       +1     
============================================
  Files           127      127              
  Lines          5354     5366      +12     
  Branches        675      680       +5     
============================================
+ Hits           3953     3959       +6     
- Misses         1104     1106       +2     
- Partials        297      301       +4     

Impacted Files	Coverage Δ
...lin/org/opensearch/commons/alerting/model/Alert.kt	74.74% <62.50%> (-0.72%)	⬇️

... and 1 file with indirect coverage changes

[lezzago]

Shouldn't this be optional? Normal monitor executions will fail when creating an alert since workflows are not there. Also the vice versa might be an issue since the chained alert won't have a monitor id.

[eirsep]

monitor id would be null or empty for chained alerts
workflow Id would be null or empty for non-workflow alert

in the constructors we handle each case and set "" to handle the empty case for either field

[opensearch-trigger-bot]

The backport to 2.5 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/common-utils/backport-2.5 2.5
# Navigate to the new working tree
pushd ../.worktrees/common-utils/backport-2.5
# Create a new branch
git switch --create backport-463-to-2.5
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 110bf0158417c3e06d08fafe6ebdccf900aecd0d
# Push it to GitHub
git push --set-upstream origin backport-463-to-2.5
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/common-utils/backport-2.5

Then, create a pull request where the base branch is 2.5 and the compare/head branch is backport-463-to-2.5.

[opensearch-trigger-bot]

The backport to 2.9 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/common-utils/backport-2.9 2.9
# Navigate to the new working tree
pushd ../.worktrees/common-utils/backport-2.9
# Create a new branch
git switch --create backport-463-to-2.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 110bf0158417c3e06d08fafe6ebdccf900aecd0d
# Push it to GitHub
git push --set-upstream origin backport-463-to-2.9
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/common-utils/backport-2.9

Then, create a pull request where the base branch is 2.9 and the compare/head branch is backport-463-to-2.9.

[opensearch-trigger-bot]

The backport to 2.7 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/common-utils/backport-2.7 2.7
# Navigate to the new working tree
pushd ../.worktrees/common-utils/backport-2.7
# Create a new branch
git switch --create backport-463-to-2.7
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 110bf0158417c3e06d08fafe6ebdccf900aecd0d
# Push it to GitHub
git push --set-upstream origin backport-463-to-2.7
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/common-utils/backport-2.7

Then, create a pull request where the base branch is 2.7 and the compare/head branch is backport-463-to-2.7.

[opensearch-trigger-bot]

The backport to 2.11 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/common-utils/backport-2.11 2.11
# Navigate to the new working tree
pushd ../.worktrees/common-utils/backport-2.11
# Create a new branch
git switch --create backport-463-to-2.11
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 110bf0158417c3e06d08fafe6ebdccf900aecd0d
# Push it to GitHub
git push --set-upstream origin backport-463-to-2.11
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/common-utils/backport-2.11

Then, create a pull request where the base branch is 2.11 and the compare/head branch is backport-463-to-2.11.