[Improvement] Make kyuubi-spark-connector tpch and tpcds easy to benchmark

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

### Search before asking

- [X] I have searched in the [issues](https://github.com/apache/kyuubi/issues?q=is%3Aissue) and found no similar issues.

### What would you like to be improved?

Let's say a step of people who want to do some benchmark:
1. materialize data with a scale factor
2. run single query or all queries with tpch/tpcds and specify iterations
3. get the benchmark report

So, we can support the follow command:
```
-- e.g., setup tpch sf1 database tpch_sf1
SETUP [TPCH|TPCDS] target_sf DATABASE target_database.

-- e.g., run tpch q1 iterations 3
-- e.g., run tpch all iterations 3
RUN [TPCH|TPCDS] [ALL|target_query] (ITERATIONS target_iterations)
```

### How should we improve?

_No response_

### Are you willing to submit PR?

- [ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
- [ ] No. I cannot submit a PR at this time.

Start by locating the kyuubi-spark-connector's existing TPCH and TPCDS benchmark entry points and how benchmark reports are currently produced. Define how SETUP and RUN should handle scale factors, databases, query selection, and iterations; done means both suites can be materialized, run for one or all queries, and produce a benchmark report.

Written by the indexing model from the issue text.