Bugfix - BitmapIndexQuery and BitmapDocValuesQuery to support negative values

[surajnayak]

Bugfix - BitmapIndexQuery and BitmapDocValuesQuery to support both +ve and -ve values in same query. also add test cases for negative set of bitmaps.

Description

• Changes BitmapIndexQuery to use bitmap.getSignedIntIterator() instead of bitmap.getIntIterator()
• Changes BitmapDocValuesQuery to set max with unsigned int representation of signed integer. and adds 2^32 if the value is < 0 in matches method

Related Issues

Resolves #18422

• [BUG] Bitmap filtering inconsistent behaviour for unsigned integer values greater than Integer.MAX_VALUE #18422

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

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 5ddd8bf: null

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?

[opensearch-trigger-bot]

This PR is stalled because it has been open for 30 days with no activity.

[github-actions]

❌ Gradle check result for 5ddd8bf: 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?

[msfroh]

@surajnayak -- Are the negative values here behaving like positive integers greater than Integer.MAX_VALUE?

On #18422, I was thinking that we should just disallow negative values for these filters. If/when we add an unsigned_int field type, we could support values between 2^31 and 2^32 - 1.