feat:migrate select tests from DuckDB

[Gump9]

I hereby agree to the terms of the GreptimeDB CLA

What's changed and what's your intention?

migrate select sqlness test from DuckDB

Checklist

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

#1168

[evenyag]

Hi, we are going to switch to the main branch, as mentioned in #3025.

I have changed the base branch of this PR to main.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.07%. Comparing base (9282e59) to head (93f8e3f).
Report is 689 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2478      +/-   ##
==========================================
- Coverage   85.27%   85.07%   -0.20%     
==========================================
  Files         729      914     +185     
  Lines      115964   152792   +36828     
==========================================
+ Hits        98889   129995   +31106     
- Misses      17075    22797    +5722     

[tisonkun]

Close as stale. It seems our codebase evolves a lot and need a rebase for this patch.

@waynexia It seems our sqlness cases are coupled. The state in former SQL file will be conveyed to the latter ... How can we test new cases in a brand new environment?

[waynexia]

Close as stale. It seems our codebase evolves a lot and need a rebase for this patch.

@waynexia It seems our sqlness cases are coupled. The state in former SQL file will be conveyed to the latter ... How can we test new cases in a brand new environment?

You can run the new cases only with -t param. But generally, a case should clean its state to avoid having side affect on others.