Query architecture improvements

[roji]

Done in 11

• Remove SqlExpressionVisitor #37533
• Allow table-valued functions to accept non-scalar parameters #37535

High priority

• Stop remapping lambda bodies to deal with parameters #35038
• Stop referencing the query from ProjectionBindingExpression in the shaper #32980
• Make our SQL tree fully immutable #32927

Backlog

• Consider not transforming member access to EF.Property in query pipeline #36785
• Clean up nullable value type handling in RelationalProjectionBindingExpresisonVisitor #36572
• Clean up JsonScalarExpression and JsonQueryExpression #36392
• Use inheritance instead of annotations for TableExpressionBase (specifically temporal tables) #33044
• Query: Re-evaluate concept of pending selector in nav expansion #20291
  • Consider removing nav expansion as a way to tackle the pending selector problem  #32957
• Consider having a common relational representation for OPENJSON, json_each and so on #32576
• Stop referencing SelectExpression _projectionBindings (and similar) from shaper
  • Allow standalone set operations (and ValuesExpression) without a wrapping SelectExpression #32890
  • Cosmos: Reimplement ReadItem via its own expression type again #34157
• Consider doing property/navigation binding entirely from RelationalSqlTranslatingExpressionVisitor #31309
• Consider introducing nullability on SqlExpression #33889
• DRY around getting the projection from ShapedQueryExpression #31015
• Remove SelectExpression private logic out to the translation visitors, making it a minimal, regular expression node #31049
• Query: convert identifiers to be generic SqlExpressions rather than ColumnExpressions #31326
• Query: Pay your (technical) debt on time #18923
• Share optimizations between relational and non-relational providers #34152

See #34524 for improvements done in 10.