Improve doc on lowercase treatment of columns on SQL

[nanicpc]

Adds specific note on lowercase treatment of columns on SQL

Which issue does this PR close?

Closes #2374

Rationale for this change

This example is the first thing newcomers see when they start with datafusion (literally the second page on the docs) so it should be clearer.

What changes are included in this PR?

Improvements on the Documentation:

• the "Example Usage" case
• the SELECT page of SQL

[alamb]

Thank you @nanicpc -- I think the notes are great. I am not sure about the change to the example code.

[alamb]

This note is great

[codecov-commenter]

Codecov Report

Merging #3385 (21487dd) into master (d16457a) will increase coverage by 0.00%.
The diff coverage is n/a.

❗ Current head 21487dd differs from pull request most recent head d39cbdd. Consider uploading reports for the commit d39cbdd to get more accurate results

@@           Coverage Diff           @@
##           master    #3385   +/-   ##
=======================================
  Coverage   85.58%   85.58%           
=======================================
  Files         296      296           
  Lines       54175    54187   +12     
=======================================
+ Hits        46364    46377   +13     
+ Misses       7811     7810    -1     

Impacted Files	Coverage Δ
...fusion/optimizer/src/single_distinct_to_groupby.rs	98.33% <0.00%> (+0.11%)	⬆️
datafusion/expr/src/logical_plan/plan.rs	77.61% <0.00%> (+0.16%)	⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[alamb]

Marking as draft to signify this PR has planned changes (and make it easier to find PRs that are in need of review). Please mark "ready for review" when it is next ready or if this change was a mistake.

[alamb]

Thanks @nanicpc

[alamb]

What do you think about changing the introductory example in the user guide @andygrove ? Given it is the first thing some people see I think there is a potential reason to keep it as simple as possible (and thus maybe it would be nice to leave it uncapitalized, and add add a link about the important subtlety of capitalization to somewhere later?

If you agree I will merge this PR and then make a follow on PR that tries to retain the simple initial example as well as the capitalized example

[andygrove]

What do you think about changing the introductory example in the user guide @andygrove ? Given it is the first thing some people see I think there is a potential reason to keep it as simple as possible (and thus maybe it would be nice to leave it uncapitalized, and add add a link about the important subtlety of capitalization to somewhere later?

If you agree I will merge this PR and then make a follow on PR that tries to retain the simple initial example as well as the capitalized example

That sounds great. Thanks @alamb

[alamb]

Thanks again @nanicpc

[ursabot]

Benchmark runs are scheduled for baseline = d5c361b and contender = d5e6736. d5e6736 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]

Follow on PR in #3815