Added @dbwiddis to OpenSearch maintainers

[owaiskazi19]

Description

I nominated Dan Widdis (@dbwiddis) to be a co-maintainer for Opensearch through our nomination process. The maintainers have agreed, and Dan has kindly accepted.

Dan is already a maintainer of opensearch-sdk-java and working actively on Extensibility. Dan has authored several PRs on OpenSearch repo. Few of them got merged to feature/extensions branch and then later to main.

1. Add DynamicActionRegistry to ActionModule
2. Update ExtensionRestResponse to handle RestRequest object
3. Only store names of extension transport actions
4. Handle Deprecated and Replaced Routes in Extension Rest Handlers
5. getSettings extension point support

Dan is active almost daily in the project, thoughtfully reviewing and commenting on pull requests (example). He has also closed 19 issues on core repo.

Few other contributions done by Dan:

1. Avoid negative memory result in IndicesQueryCache stats calculation
2. Don't register destructiveDistroTest.docker twice
3. Remove deprecated org.gradle.util.DistributionLocator usage
4. Include Windows OS in Bootstrap initializeNatives() check for definitelyRunningAsRoot()

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)

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 (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/15928/
• CommitID: ba98184
  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 (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/15930/
• CommitID: 9af7715
  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 (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/15931/
• CommitID: a89e31e
  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?

[nknize]

> Task :server:jarHell FAILED
| Output for C:\hostedtoolcache\windows\Java_Adopt_jdk\11.0.19-7\x64\bin\java.exe:#
# There is insufficient memory for the Java Runtime Environment to continue.

Sheesh! Brittle! Can't even pass a maintainers update. 🤦🏻‍♂️

Re-firing

[nknize]

DiskThresholdDeciderIT strikes again... Love it when we're trolled by flakes.

./gradlew ':server:internalClusterTest' --tests "org.opensearch.cluster.routing.allocation.decider.DiskThresholdDeciderIT.testIndexCreateBlockIsRemovedWhenAnyNodesNotExceedHighWatermarkWithAutoReleaseEnabled" -Dtests.seed=62BA04CB1F0111FC -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=pl -Dtests.timezone=Indian/Chagos -Druntime.java=19

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/15949/
• CommitID: a89e31e
  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 (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/15991/
• CommitID: a89e31e
  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?

[dblock]

Do we need to add @dbwiddis to CODEOWNERS too?

I adjusted permissions.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/16062/
• CommitID: 496fe13
  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 (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/16086/
• CommitID: d56ee9a
  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 (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/16094/
• CommitID: 2a08c9d

[codecov]

Codecov Report

Merging #7665 (2a08c9d) into main (b4b3724) will increase coverage by 70.82%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main    #7665       +/-   ##
===========================================
+ Coverage        0   70.82%   +70.82%     
- Complexity      0    56158    +56158     
===========================================
  Files           0     4680     +4680     
  Lines           0   266081   +266081     
  Branches        0    39067    +39067     
===========================================
+ Hits            0   188439   +188439     
- Misses          0    61684    +61684     
- Partials        0    15958    +15958     

see 4680 files with indirect coverage changes

[dblock]

Everything looks good.

@xuezhou25 please speak reach out if you want your maintainer permissions restored - that was automatically adjusted when leaving the org

[opensearch-trigger-bot]

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

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

[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-7665-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f640c40becb8cf18e61442fa205ad77d02d5b283
# Push it to GitHub
git push --set-upstream origin backport/backport-7665-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-7665-to-2.x.