fix: Visit subqueries in Expr::Alias

[askoa]

Which issue does this PR close?

Closes #4898

Rationale for this change

See issue description.

Are these changes tested?

Yes. A new test is included to test the changes.

Are there any user-facing changes?

The users who enable tracing of LogicalPlan might see additional subqueries in the logs.

[alamb]

👍 thanks @askoa

I wonder if this would be easier to implement if we had some sort of function / visitor that walked a LogicalPlan and visited all expressions as I was discussing with @avantgardnerio on #4701 (comment)

I'll see if I can give it a try

[ursabot]

Benchmark runs are scheduled for baseline = dee0dd8 and contender = 42c81be. 42c81be is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ec2-t3-xlarge-us-east-2] ec2-t3-xlarge-us-east-2
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on test-mac-arm] test-mac-arm
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-i9-9960x] ursa-i9-9960x
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-thinkcentre-m75q] ursa-thinkcentre-m75q
Buildkite builds:
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

[alamb]

BTW here is a follow on proposal to avoid bugs like this in the future: #4906

[askoa]

BTW here is a follow on proposal to avoid bugs like this in the future: #4906

Seems like a nice way to consolidate the approach.