fix(substrait): Allow scalar subquery in projection

[bvolpato]

Which issue does this PR close?

• Closes [substrait] Scalar subquery in select not supported #18066.

Rationale for this change

Recent validations added at #15334 started to cause problems for some LEFT JOIN queries that don't have conditions, for example:

SELECT a, (SELECT MAX(b) FROM data2) as max_b FROM data

This query gets optimized as a left join without conditions.

This basically follows the same approach from #15334 :

datafusion/datafusion/optimizer/src/scalar_subquery_to_join.rs

Line 345 in a65a2cb

vec![Expr::Literal(ScalarValue::Boolean(Some(true)), None)],

What changes are included in this PR?

For joins without conditions, use cross_join if inner, otherwise use a filter with Boolean(true)

Are these changes tested?

Added a roundtrip test case.

Are there any user-facing changes?

n/a

[gabotechs]

One thing to take into account is that Postgres does not allow this. In Postgres, it's invalid to provide an inner join without a join condition (although other DBs like MySQL allow it).

My impression is that the change in #15334 was actually trying to adhere to this standard, which is a fair decision, so that means that probably the Substrait path should also adhere to that standard, unless there's a strong reason to diverge.

Don't have a strong opinion about whether if we should automatically convert inner joins without conditions to cross joins or not, but I'd advocate for consistency in both the normal SQL path and the Substrait path