minor: Improve error message for invalid column expression in SELECT statement

[2010YOUY01]

Which issue does this PR close?

• Closes #.

Rationale for this change

User friendly 'did you mean' error message is missing for some cases, this PR fixes it.

Demo in datafusion-cli

-- Before
> create external table hits
stored as parquet
location '/Users/yongting/Code/datafusion/benchmarks/data/hits_partitioned';
0 row(s) fetched.
Elapsed 0.056 seconds.

> select url+1 from hits;
Schema error: No field named url. Valid fields are hits."WatchID", hits."JavaEnable", hits."Title", hits."GoodEvent", hits."EventTime", hits."EventDate", hits."CounterID", hits."ClientIP", hits."RegionID", hits."UserID", hits."CounterClass",
...

-- PR
> select url from hits;
Schema error: No field named url. Did you mean 'hits."URL"'?
Column names are case sensitive. You can use double quotes to refer to the hits."URL" column or set the datafusion.sql_parser.enable_ident_normalization configuration.
Valid fields are hits."WatchID", hits."JavaEnable", hits."Title", hits."GoodEvent", hits."EventTime", hits."EventDate", hits."CounterID", hits."ClientIP", hits."RegionID", hits."UserID", hits."CounterClass", hits."OS", hits."UserAgent", hits."URL", hits."Referer", hits."IsRefresh", hits."RefererCategoryID", hits."RefererRegionID", hits."URLCategoryID", hits."URLRegionID",
...

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

[2010YOUY01]

Now this case sensitive hint only shows up, if the input expr has some case-insensitive match.