[BUG] Add Unit Test for Cardinality Aggregation for different scorer paths

[expani]

Describe the bug

While upgrading to Lucene 10.2.1, we observed an exception with cardinality-agg-low/high operation in Big5 workload.

See stack trace #17961 (comment)

Since, the query for cardinality-agg-low/high is MatchAllDocsQuery -> which produces a -> ConstantScoreWeight -> creates a -> ConstantScorerSupplier -> creates a -> DenseConjunctionBulkScorer for some cases unlike DefaultBulkScorer in all cases in older versions.

This change was introduced in Lucene 10.2.0 with https://github.com/apache/lucene/pull/14359/files

We need to add a unit test which covers the same and any other assumption which might not hold true after upgrade.

cc: @bowenlan-amzn

Related component

Search

To Reproduce

#17961 (comment)

Expected behavior

Unit test should catch this case instead of showing up in Big5 workload

Additional Details

No response