Backport #1024 tenant resolver

[rutuja-amazon]

Backport #1024 to branches "1.3", "1.2", "1.1", 1.0"/
Follow up issue: #1012

Check List

• New functionality includes testing
• New functionality has been documented
• 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.

[rutuja-amazon]

@DarshitChanpura @peternied this PR had to be tagged with "backport 1.3", "backport 1.2", "backport 1.1", "backport 1.0" before merging.

[opensearch-trigger-bot]

The backport to 1.3 failed:

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

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

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

[peternied]

@rutuja-amazon It looks like nearly all of those backports had issues, if you'd like to see them merged please investigate them.

[rutuja-amazon]

@peternied I'm looking into why auto-backporting is causing issues.