[Feature][connector-jdbc] Optimize unit testing of jdbc connector code

### Search before asking

- [x] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement.

### Description

### Problem
1. At present, the unit tests of connector-jdbc code basically rely on the local environment and will be turned off during the actual running of ci, which will lead to functional risks. We hope to introduce docker containers and run unit tests in the actual ci process.
2. The unit test coverage of connector-jdbc code is relatively low, such as the jdbcCatalog test and jdbcDialect test. Additionally, there is a lack of boundary condition test cases. We hope to add relevant test cases.
3. After completing points 1 and 2, you can transfer the unit tests in the jdbc-e2e module to connector-jdbc.

### Implementation scope
| type | status |Assignees |
| -------------- | ---- | ---- |
| mysql | | |
| oracle | | |
| pgsql | | |
| sqlserver | | |
| dameng | | |
| db2 | | |
| kingbase | | |
### Usage Scenario

_No response_

### Related issues

_No response_

### Are you willing to submit a PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

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

Start by reviewing the connector-jdbc unit tests, especially jdbcCatalog and jdbcDialect, along with the jdbc-e2e module and the CI configuration. Check how tests currently depend on the local environment and which database types are covered. Done means boundary cases are added, Docker-backed tests run in CI, and applicable jdbc-e2e tests are moved into connector-jdbc.

Written by the indexing model from the issue text.