Add new query profile collector fields with concurrent search execution

[ticheng-aws]

Description

To show high-level concurrent execution details, we bring min_slice_time_in_nanos, max_slice_time_in_nanos, and slice_count etc. fields into the query response. With these new fields, users can quickly determine query performance and skew issues.

Definition of existing collector fields

name: A more friendly representation of the collector's class name.
reason: A "hint" to help provide some context about this collector.
time_in_nanos: The total elapsed time for this collector. In the concurrent search case, this is the total time across all slices (i.e. max(slice_end_time) - min(slice_start_time))
children: A list of children collectors "embedded" inside this collector.

Definition of new collector fields with concurrent execution

reduce_time_in_nanos: The elapsed time in the reduce phase.
min_slice_time_in_nanos: The minimum slice time for this collector manager.
max_slice_time_in_nanos: The maximum slice time for this collector manager.
avg_slice_time_in_nanos: The average slice time for this collector manager.
slice_count: The segment slice count for this collector manager.

Related Issues

Resolves #7355
Doc update issue: opensearch-project/documentation-website#4281

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/16760/
• CommitID: 8269e42
  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/16761/
• CommitID: 00d2519
  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/16779/
• CommitID: c45a836
  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/17081/
• CommitID: 1cd9337

[sohami]

[DOC] Update search profile API documentation with concurrency related changes opensearch-project/documentation-website#4281

@reta Just wanted to confirm that this doc change will be needed as part of concurrent search GA not before that. This is because the output of profile will not show these fields before that.

[reta]

[DOC] Update search profile API documentation with concurrency related changes opensearch-project/documentation-website#4281

@reta Just wanted to confirm that this doc change will be needed as part of concurrent search GA not before that. This is because the output of profile will not show these fields before that.

@ticheng-aws That is fine, you could mention the version this feature will be available

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/17084/
• CommitID: d308c36
  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: null ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/17086/
• CommitID: 77fb125
  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: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.search.backpressure.SearchBackpressureIT.testSearchShardTaskCancellationWithHighCpu

• URL: https://build.ci.opensearch.org/job/gradle-check/17095/
• CommitID: 5eedf6e
  Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/17101/
• CommitID: e5ba28c

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

[reta]

@ticheng-aws mind please to submit a manual backport to 2.x branch?

[ticheng-aws]

@ticheng-aws mind please to submit a manual backport to 2.x branch?

#7975 backport for this PR has been created.