Add Release Notes for 2.19.0

[junweid62]

Description

[Add Release Notes for 2.19.0]

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.47%. Comparing base (6d6116d) to head (c581d68).
Report is 1 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #1036      +/-   ##
============================================
- Coverage     75.53%   75.47%   -0.06%     
  Complexity     1050     1050              
============================================
  Files           101      101              
  Lines          5215     5215              
  Branches        498      498              
============================================
- Hits           3939     3936       -3     
- Misses         1038     1042       +4     
+ Partials        238      237       -1     

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

[owaiskazi19]

Thanks for adding this @junweid62. Can you run ./gradlew spotlessApply and push again?

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

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

[opensearch-trigger-bot]

The backport to 2.19 failed:

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

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

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

[owaiskazi19]

@junweid62 can you backport this to 2.x and 2.19 branch?