Avoid search_after short cutting in case of missing is specified

[gashutos]

Description

Fix for #8212.
If missing is specified in sort queries like below, it should result documents with null values as well in last. With #7453 optimizations of min/max values short cutting, this is breaking beucase if shard/segment has its min/max values out of search_after range but can still have missing values those are qualified for the output result.

{
	"size": 5,
	"sort": [{
		"amount_cents": {
			"order": "desc",
			"missing": "_last"
		}
	}, {
		"id": {
			"order": "desc",
			"missing": "_last"
		}
	}],
	"search_after": [150, "2"],
	"track_total_hits": false,
	"_source": false
}

Related Issues

Resolves #8212

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/18860/
• CommitID: 0a3a30e
  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.snapshots.RestoreSnapshotIT.testRestoreRemoteStoreIndicesWithoutRemoteTranslog
      1 org.opensearch.snapshots.RestoreSnapshotIT.testRestoreRemoteStoreIndicesWithRemoteTranslog
      1 org.opensearch.snapshots.RestoreSnapshotIT.testRestoreRemoteStoreIndicesWithRemoteTranslog
      1 org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testNodeDropWithOngoingReplication

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

[codecov]

Codecov Report

Merging #8391 (2d25462) into main (665d237) will decrease coverage by 0.04%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##               main    #8391      +/-   ##
============================================
- Coverage     70.95%   70.92%   -0.04%     
+ Complexity    56943    56937       -6     
============================================
  Files          4757     4757              
  Lines        269125   269125              
  Branches      39403    39403              
============================================
- Hits         190955   190872      -83     
- Misses        62079    62186     +107     
+ Partials      16091    16067      -24     

Impacted Files	Coverage Δ
...main/java/org/opensearch/search/SearchService.java	71.90% <0.00%> (-0.77%)	⬇️

... and 448 files with indirect coverage changes

[gashutos]

@dblock @reta when you guys get chance.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

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

      2 org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testNodeDropWithOngoingReplication
      2 org.opensearch.remotestore.RemoteStoreRefreshListenerIT.testRemoteRefreshRetryOnFailure
      1 org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testDropPrimaryDuringReplication

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

[dbwiddis]

LGTM

[opensearch-trigger-bot]

The backport to 2.x 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-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-8391-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 240193a8b129aaffffb39a57403264b8c4893efb
# Push it to GitHub
git push --set-upstream origin backport/backport-8391-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-8391-to-2.x.