Add 2PR approval to release workflow

[gaiksaya]

Description

This change retrieves the codeowner's list from .github/codeowners file and adds them as approvers for releasing opensearch-java.
Here is a sample issue that is created when this workflow runs: gaiksaya#1
Once approved, the workflow continues to run as usual.
Note: This approval duration is subject to the broader 72 hours timeout for a workflow.

Issues Resolved

related opensearch-project/opensearch-build#3111
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.

[dblock]

This is cool, but I think I don't understand why we don't just make release-drafter a manually kicked off workflow (that can be kicked off by maintainers only already)?

[dblock]

Oh it's to have 2 (TWO) approvers. I get it now. Let's add it to CHANGELOG (e.g. "Require 2 maintainers to approve a release.").

[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:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-383-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c562e7ce69e1333b1a15b0b60f84b4b7974f884e
# Push it to GitHub
git push --set-upstream origin backport/backport-383-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x

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