Fix wrong results bug with count over mixed aggregation

Description

Fix a wrong results bug with count over an aggregation that had a mix of global and non-global grouping sets.

We were not checking for single global aggregations correctly in QueryCardinalityUtil, so we would return that the plan was scalar if there were any empty grouping sets rather than if the empty grouping set was the only grouping set. we have now fixed this to return that if all of the grouping sets are global, then the cardinality will be the number of grouping sets, and otherwise it is at least the number of global grouping sets.

This fixes queries like the following:

SELECT COUNT(*) FROM (SELECT count(*) FROM tpch.sf1.nation GROUP BY GROUPING SETS (nationkey, ()));

previously we would incorrectly return 1. And now we return 26.

This change may also fix bugs with correlated subqueries, as those also use the isScalar() utility function.

Motivation and Context

Fixes https://github.com/prestodb/presto/issues/22977

Impact

Fixes wrong results for queries with counts over mixed global and grouped aggregations .e.g. SELECT COUNT(*) FROM (SELECT count(*) FROM tpch.sf1.nation GROUP BY GROUPING SETS (nationkey, ()));

Test Plan

added unit tests

Contributor checklist

[ ] Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
[ ] PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
[ ] Documented new properties (with its default value), SQL syntax, functions, or other functionality.
[ ] If release notes are required, they follow the release notes guidelines.
[ ] Adequate tests were added if applicable.
[ ] CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

General Changes
* Fix a bug where count queries on top of aggregations with mixed global and grouped grouping sets could return wrong results.

prestodb / presto