JVM module runtime connects directly to controller instead of runner

[matt2e]

The aim was for the runner to proxy all messages for the controller for now, but it doesn't seem to be happening.

Turns out FTLController is connecting to the controller address not the runner address:

FTLController() {
        String endpoint = System.getenv("FTL_ENDPOINT");
        ... this points to http://127.0.0.1:8892/...

This came up because messages sent to publish's service gets 404'd as it is not present in the controller but is in the runner.

Steps to repro:
ftl serve
ftl deploy ./backend/controller/pubsub/testdata/java
ftl call publisher.publishTen