Pushed containerimage by default sets LIVEKIT_JWT_PORT to a value

[MTRNord]

Describe the bug
For unknown reasons ghcr.io/element-hq/lk-jwt-service:0.2.3 seems to not behave like the pushed code.

Starting it results in:

2025/05/08 10:09:52 LIVEKIT_URL: wss://<redacted>.livekit.cloud, LIVEKIT_JWT_PORT: tcp://10.43.219.85:8080
2025/05/08 10:09:52 listen tcp: address :tcp://10.43.219.85:8080: too many colons in address
Stream closed EOF for matrix/livekit-jwt-5cd5f94bdf-mzt2x (livekit-jwt)

However we dont set LIVEKIT_JWT_PORT and according to the codebase the container doesnt either. Did someone maybe manually push it and forgot to push changes?

To Reproduce
Steps to reproduce the behavior:

1. Run the container image

Expected behavior
It uses the default 8080 port or at least a valid value.

[HarHarLinks]

specifically image ghcr.io/element-hq/lk-jwt-service@sha256:a0823807b7d72df7739e31f4d39004d8c87c39d8736b45627c7af6a5d7604054