[Bug] Undeterminstic behavior for not exist schema in JDBC URL

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

bin/beeline -u 'jdbc:hive2://10.221.102.180:10009/tpcds/balab 👍
bin/beeline -u 'jdbc:hive2://10.221.102.180:10009/balab 👎

Case 1 uses our tpcds catalog but passed unexpectedly with a nonexistent db, while case 2 use `spark_catalog` failed expectedly

### Affects Version(s)

master

### Kyuubi Server Log Output

_No response_

### Kyuubi Engine Log Output

_No response_

### Kyuubi Server Configurations

_No response_

### Kyuubi Engine Configurations

_No response_

### Additional context

_No response_

### Are you willing to submit PR?

- [ ] 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.

Reproduce the two JDBC URLs with bin/beeline and compare how the catalog and nonexistent schema are resolved. Trace the JDBC URL handling and schema validation path, then identify the expected behavior for both cases. Done means a nonexistent schema is handled consistently, with a regression test covering the two URLs.

Written by the indexing model from the issue text.