[BUG] incorrectly recognizes --hivevar parameters as hiveconf when using HIVE_SQL

### 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.

### Describe the bug

The version in use is 1.9.1, and kyuubi.engine.type=HIVE_SQL.

I use the following command to connect to Kyuubi:
./beeline -u 'jdbc:hive2://192.28.16.177:10009' --hivevar table_dt=20241113 -n xxxxx -p yyyyyyy

From the logs, we can see that the value of table_dt is passed via -conf:



When using the set command to print all variables, everything is displayed, and we can see that table_dt’s type is conf instead of hivevar:



However, if we connect directly to HiveServer2 for testing:

./beeline -u 'jdbc:hive2://192.28.18.38:7001' --hivevar tabel_dt=20241113 -n xxxxxx -p yyyyyyy

Using the set command, we can see that the variable tabel_dt is of type hivevar:


In Hive:
• hiveconf is typically used for configuration or system-level parameters. It can also be referenced in queries within scripts.
• hivevar is mainly used for user-defined variables that can be referenced in queries but does not directly affect Hive’s own configuration.

If we treat a hivevar as hiveconf directly, problems can easily occur.

### Affects Version(s)

1.9.1

### Kyuubi Server Log Output

```logtalk

```

### Kyuubi Engine Log Output

```logtalk

```

### Kyuubi Server Configurations

```yaml

```

### Kyuubi Engine Configurations

```yaml

```

### Additional context

_No response_

### Are you willing to submit PR?

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