fix(substrait): Do not add implicit groupBy expressions when building logical plans from Substrait

[anlinc]

Which issue does this PR close?

Closes #14348

Rationale for this change

Substrait plans are intended to be interpreted literally. When you see plan nodes like:

"project": {
  "common": {
    "emit": {
      "outputMapping": [0, 3]
    }
  },
...
}

The output mapping (e.g. [0, 3]) contains ordinals representing the offset of the target expression(s) within the [input, output] list. If the DataFusion LogicalPlanBuilder is introducing additional input expressions, this violates the plan's intent and will produce the incorrect output mappings. Please see the issue for a concrete example.

What changes are included in this PR?

• Introduce new add_implicit_group_by_exprs option to the logical plan builder. It is disabled by default.
  • The option is enabled only in the DataFrame and SQL paths.

Are these changes tested?

Added a multilayer aggregation Substrait example. The first aggregation produces a unique column with a functional dependency. Despite this, the second aggregation must not introduce any additional grouping expressions.

There should be no changes in the non-Substrait paths.

Are there any user-facing changes?

No.

Appendix

This is a continuation of #14553.

[alamb]

Thank you @anlinc

I think this looks great to me

cc @Blizzara @vbarua

[alamb]

Hi @anlinc

It looks like there is a small clippy failure with this PR:

https://github.com/apache/datafusion/actions/runs/13507870042/job/37742937287?pr=14860