Support jdbc and proxy use together in e2e test.

## Feature Request

The current test of e2e is to utilize the docker environment, and the intercommunication between different components is through the alias of the docker container. However, since the startup of JDBC is a test program that relies on E2E, it cannot rely on the alias of the container when communicating with the proxy.
This problem leads to the failure of e2e testing in some scenarios where proxy and jdbc are deployed together.

## Possible solutions
- make jdbc as a docker container.
- Let the communication between containers rely on the real ip, so that jdbc can also rely on this ip for communication

Start by locating the e2e test setup for JDBC and proxy communication in the Docker environment. Compare the current container-alias communication with the two proposed approaches: containerizing JDBC or using real container IPs. Done means e2e scenarios with proxy and JDBC deployed together pass reliably.

Written by the indexing model from the issue text.