Fix/improve wildcard error 15004

[Jiashu-Hu]

Which issue does this PR close?

• Closes #15004.

Rationale for this change

The current error messages for non-aggregate columns in GROUP BY queries are technically accurate but not user-friendly. They use technical terminology like "non-aggregate values" without clearly explaining the problem or providing actionable solutions. This PR improves these error messages to be more intuitive and helpful, especially for users who might not be familiar with SQL aggregation concepts.

What changes are included in this PR?

added two function in to expand_wildcard_rule.rs:

1. fn check_group_by_info(input: &LogicalPlan) -> (bool, Vec<Expr>, Vec<Expr>)

• Detects if a query contains a GROUP BY clause
• Collects columns used in GROUP BY and in aggregate functions
• Returns a tuple of (has_group_by, group_by_columns, aggregate_columns)

2. fn validate_columns_in_group_by_or_aggregate(has_group_by: bool, expanded: &Vec<Expr>, group_by_columns: &Vec<Expr>, aggregate_columns: &Vec<Expr>) -> Result<(), DataFusionError>

• Verifies all selected columns appear either in the GROUP BY clause or within aggregate functions
• Returns a clear SchemaError::GroupByColumnInvalid error when validation fails

3. added a new SchemaError type to shows the error message - datafusion_common::SchemaError::GroupByColumnInvalid

In datafusion/sql/src/utils.rs:

• Updated message_prefix() method to provide clearer error message prefixes
• Improved help text in check_column_satisfies_expr() to suggest specific solutions
• for easy understanding as requested in #15004

Are these changes tested?

• The new validation functions in expand_wildcard_rule.rs have been tested with test cases included at the bottom of the file. These tests verify both successful validation and proper error reporting.
• The message improvements in datafusion/sql/src/utils.rs modify only the error text, not the functional logic, so no additional tests were added for these changes.

Additional test cases are welcome to ensure comprehensive coverage.

Are there any user-facing changes?

Yes. Users will now see more intuitive error messages when they encounter GROUP BY validation issues. For example, instead of seeing:

Error during planning: Projection references non-aggregate values: Expression foo.b could not be resolved from available columns: foo.a

They will see:

Error during planning: Column in SELECT must be grouped or aggregated: Expression foo.b could not be resolved from available columns: foo.a

This change makes errors more understandable and provides clearer guidance on how to fix the issue.

[alamb]

The CI seems to be failing so marking as draft for now. Please mark it ready for review when ready for another look