chore!: Unify local and remote ports of Clickhouse

More often than not there is user error introduced when trying to connect to Clickhouse through GDK or locally, because each use a different port depending on the type of access.

Cube already binds the local port 4000 to the exact same port on the container. Clickhouse should follow suit.

Only downside of this is for those doing infrastructure work which might have the same ports forwarded via kubectl, but I'd highly recommend against running the devkit and forwarding ports from a Kubernetes cluster just to avoid confusing which environment you're in.

BREAKING CHANGE: Use port 8123/9000 when needing to access Clickhouse in your local environment.