Update the DEVELOPER_GUIDE.md to add Gradle Check Metrics Dashboard details

[prudhvigodithi]

Description

Coming from #11217 (comment) and #11217 (comment) update the DEVELOPER_GUIDE.md to add Gradle Check Metrics Dashboard details.

Related Issues

Part of #11217

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.

[reta]

@andrross @prudhvigodithi I think it belongs to CONTRIBUTING.md more, since the DEVELOPER_GUIDE.md is all about local development, and not shared CI infra (like Jenkins, GA checks, etc) or README.md

[prudhvigodithi]

Hey @reta the DEVELOPER_GUIDE.md already has information about the flaky tests that has the details mentioning about the CI checks and gradle workflows. The idea of this PR is ensure developers are aware of this OpenSearch Gradle Check Metrics Dashboard to help investigate the flaky failures and resolve them, so more than CONTRIBUTING.md, the DEVELOPER_GUIDE.md seems to be like the right place for this information.

[andrross]

Yeah, I think this works well alongside the "Flaky Tests" subheading in the developer guide. I'm going to merge this as-is, but we can always iterate and improve on the documentation as needed. Thanks!

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