13776: allow adding query parameters to RequestOptions

[oliverlockwood]

Description

Allows adding query parameters to RequestOptions, e.g. to be able to set ?filter-path=<something> as documented in https://opensearch.org/docs/2.3/opensearch/common-parameters/#filtered-responses.

Related Issues

Resolves #13776.

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• API changes companion pull request created.
• Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)
• 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.

[github-actions]

❌ Gradle check result for 0a5736f: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 618b4dd: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[oliverlockwood]

❌ Gradle check result for 618b4dd: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

❌ Gradle check result for 0a5736f: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

These failures are flaky tests described by, respectively, #5329 and #13600

[github-actions]

❌ Gradle check result for 963f929: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[reta]

❌ Gradle check result for 963f929: FAILURE

#13473

[github-actions]

✅ Gradle check result for e760d86: SUCCESS

[reta]

@gaobinlong any concerns from your side? thank you!

[github-actions]

✅ Gradle check result for f29c2e3: SUCCESS

[oliverlockwood]

I've just fixed the CHANGELOG merge conflict. Is there anything else required from me on this PR? @reta @gaobinlong ?

[github-actions]

✅ Gradle check result for fcfcae3: SUCCESS

[reta]

I've just fixed the CHANGELOG merge conflict. Is there anything else required from me on this PR? @reta @gaobinlong ?

LGTM to me! Thank you @oliverlockwood !

[gaobinlong]

LGTM.

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

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

[reta]

Backport #13778